Founding lifetime priceEnds in30d 00:00:00Buy Now

Troubleshooting

Common setup and runtime issues when connecting providers or publishing.

Updated

API key rejected

  • Confirm you pasted the full key with no extra spaces
  • Create a new key in the provider dashboard if the old one was revoked or never fully copied
  • Check you selected the matching provider in QueueWrite Settings
  • Use Test & Save again after replacing the key

If authentication fails during a run, QueueWrite may pause the queue and ask you to fix the key in Settings before resuming.

Writer not ready

  • Connect a writing provider and complete Test & Save
  • For OpenRouter, choose a writing model as well as pasting the key
  • Confirm the provider account can accept API requests (billing enabled / credit available)

Research failed

  • Confirm the research provider key (Tavily for web research, Consensus for academic research)
  • Check the provider account for credit or plan limits
  • Retry the article, or temporarily turn research off if you only need a draft

Provider out of credit or billing issue

When the writing provider cannot continue because of billing or credit, QueueWrite pauses the queue after the failed job. Open the provider’s billing page, resolve the account issue, then resume the queue in QueueWrite.

Queue paused because the provider cannot continue

  • Read the pause message in QueueWrite — it usually points to API Settings or provider billing
  • Fix the key or account, then resume
  • You can also pause and resume manually while you investigate

WordPress connection failed

  • Confirm the site URL is correct and the site is reachable
  • Use an Application Password from Users → Profile — not your normal WordPress password
  • Confirm the WordPress user can publish and that Application Passwords are enabled on the site
  • Use Test in Settings → Publishing, then Test & Save when the test succeeds

Website Learning issues

  • Confirm the project site URL is correct and publicly reachable
  • Use Refresh to run learning again
  • If learned context looks wrong, use Forget Website Context and learn again
  • Website Learning improves local project context; it is not a substitute for connecting a writing API
Never send API keys to QueueWrite

If you contact support, describe the error message without pasting secret keys or Application Passwords.

← Back to Help Centre