When the AI is busy, theStacc waits for you
The article-writing service can return temporary overload or rate-limit errors. For full blog generation, the retry helper waits between attempts and can update the progress message to AI service busy, retrying…. That message means another attempt is being made; it does not confirm the next attempt will succeed. The background writer uses a retry allowance of up to 30 minutes per AI call. A blog can involve more than one call, so this is not a promised completion time or one limit for the whole article. If the post remains in Generating with a retry message, avoid starting another full generation while that work is active.Use the retry shown for the failure
For a recorded overload or rate-limit failure, the post can show AI service was busy with Try again. If a retry-after hint is available, the button shows Try again in …s until its countdown ends. Wait for the enabled button; the countdown is a suggested delay, not confirmation that the service has recovered. A different Generation failed panel can show Retry instead. Both writing-retry buttons start full generation again. Before clicking, check whether useful text is already saved and whether the missing-image notice offers a narrower repair. Keep a copy of anything you want to retain. Retry controls require project-edit access, and writing retries still check subscription eligibility and applicable generation limits. If the button is absent, disabled or refused, read the access or plan message rather than repeatedly sending the request.What’s in an error, in plain terms
A structured error from theStacc’s writing service can include a code, message, retry-after hint and occurrence time. The codesai_overloaded and ai_rate_limited select the busy-service panel. The occurrence time helps the countdown account for time that passed before you refreshed the page.
Other failures can have a different code or just a message. A generic Retry button is not proof that the problem is temporary. Read whether the message concerns access, a generation allowance, an invalid request or service availability. If repeating the same action produces the same failure, keep the message and ask support for help.
If a post stops making progress
Refresh or reopen the post before treating an unchanged progress display as a stuck job. Automatic status polling has a limited window, so a quiet display alone does not establish that background work stopped. Read the refreshed status and inspect any text or images already saved. The current recovery paths use a 45-minute age threshold for some stalled generations, with a separate background sweep. The result can be Generation failed, a reviewable article with image failures, or a requeued attempt after a worker interruption. Recovery depends on the available job state and the checks running successfully; it is not a guarantee that every post changes status at exactly 45 minutes. If the refreshed post still makes no progress, note its title, project, status and displayed message when contacting support. Copy any useful saved writing before a full retry. Do not repeatedly replace a draft just because its progress display has stopped moving.When only the images failed, retry just the images
Use Retry images when the post records failed images and the writing is worth keeping. This action reuses the original image-plan entries and requests the failed images without calling the article writer again. It can fill successful results into the saved content while leaving re-failed entries flagged. The retry accepts Generated, pending review and Generation failed posts. It is blocked during active generation and after approval or publication. If there are no recorded failures, there may be nothing to retry. If an original plan entry is missing, another retry cannot reconstruct it from an instruction you entered for a separate image edit. Image-only retry skips article writing, but it still makes new image-generation requests and is not a free-retry promise. Review any account usage or billing message and inspect the recovered pictures, placeholders and featured image. See Image Generation for other replacements when the original request remains unsuitable. A full-generation safeguard redirects an older Generation failed post with saved text and failed images to Retry images. It is specific to that state, rather than a universal promise that full generation can never overwrite a saved article.Retries while you’re actively waiting
A section rewrite uses a shorter retry allowance than full blog writing: the current writing-service call has a 90-second retry budget. This is not a guaranteed response time for the whole action, and an image edit follows a different workflow. Wait for that action’s result or error before deciding what to repeat. For several selected sections, some rewrites can succeed while others fail, and successful replacements can be saved. Inspect the saved article before retrying failed sections so you do not repeat work you wanted to keep. See Regenerating Content for section and image controls.What you actually need to do
Choose the next action from the refreshed post, rather than applying the same retry to every failure. The distinction that matters is whether useful text is already saved and which part of the work failed.Choose a recovery action from the current post
| What you see | Next action | Check before repeating |
|---|---|---|
| Generating with a retry message | Let the active attempt continue | Refresh the status if progress stops updating |
| AI service was busy | Wait for Try again to become enabled | The countdown, access and whether text is saved |
| Generation failed with Retry | Read the failure, then choose a suitable retry | Any saved material you want to retain |
| Saved text with failed images | Use Retry images | Original image plan, remaining placeholders and returned errors |
| Repeated failure or no refreshed progress | Contact support with the post details | Current status and message, without credentials |
Related articles
- Blog Generation: prepare a plan, start writing and review the saved draft.
- Regenerating Content: choose a section, image or plan change.
- How the content engine works and How the AI works: the wider content workflow.
- Content SEO Overview and Blog Status Lifecycle: find the post and interpret its status.
