Article Stuck in Queue or Processing

Normal Generation Times

• Standard article: 3–5 minutes
• Longread: 10–20 minutes

If an article has been in Generating status for more than 30 minutes, something has gone wrong.

Step 1: Check the Generation Logs

1. Open the article from the Articles tab
2. Go to the Logs tab
3. Find the first step with an error status and read the error message

[SCREENSHOT: Article → Logs tab showing steps 1–8 with green checkmarks and step 9 with a red error badge and error message text]

Common Causes

• API timeout — the AI service took too long. Solution: click Retry
• Invalid API key — key expired or incorrect. Solution: update in Account settings or Site settings
• Rate limit (429) — too many requests. Solution: wait 10–15 minutes and retry
• CMS connection error — WordPress or another CMS refused the connection. Solution: test the connection in site settings
• OpenRouter balance empty (longreads only) — no credits on OpenRouter. Solution: add credits at openrouter.ai

Automatic Retry

The system automatically retries on temporary errors (5xx responses, timeouts):

• Standard pipeline: up to 2 automatic retries with a 30-second delay between attempts
• Longread pipeline: up to 3 automatic retries with a 7-second delay; also has checkpoint recovery — on the next manual retry, the pipeline resumes from the last successful step

Step 2: Manual Retry

Click Retry on the article or keyword row. Most failures resolve on the first manual retry.

[SCREENSHOT: Failed article row in the keywords table with a red Error badge and a Retry button highlighted]

Step 3: Contact Support

If the article fails 3 times in a row, screenshot the Logs tab with the error message and contact support at Support in the sidebar. Include the article title and site URL.