🔍 What Is This Issue?
Sometimes a Content Genius article can get stuck in an "Execution already in progress" state (also shown as a 409 error). When this happens, the article appears locked and every attempt to run an AI edit is blocked or automatically restarted. This is caused by a server-side process that failed mid-flight and did not release its lock on the article.
This is a known platform issue that our engineering team has identified and fixed at the system level. However, individual articles can still become stranded if they were in progress at the time of the failure. The good news: once the backend lock is cleared, your article becomes fully editable again and any AI credits consumed by the failed operation can be restored.
⚙️ What Causes This?
- The AI generation pipeline fails partway through a task (for example, during the research step) and does not clean up its progress state.
- The article remains flagged as AI_IN_PROGRESS on the server even though no active process is running.
- Any new AI edit request detects the existing flag and refuses to start, creating a loop.
✅ Steps to Resolve
- Stop retrying the edit. Repeatedly attempting to start a new AI edit while the lock is active will not help and may complicate the resolution.
- Note your article details. Before contacting support, write down the affected article name or page ID — this allows the support agent to locate and clear the lock as quickly as possible.
- Contact the Search Atlas support team via the in-app chat. This lock can only be cleared on the backend by our team. Open the chat widget inside Search Atlas, describe the stuck lock, and share the article name or page ID. A support agent will manually remove the stuck AI_IN_PROGRESS flag from the affected article on the server side and confirm once it is done. If you need help reaching the chat, type human teammate in the chat widget in the bottom-right corner of the platform to be connected with a member of our team.
- While you wait, confirm the article is truly stuck. Check whether the article status still shows the lock after waiting at least 5 minutes without any retries. If the lock clears on its own, proceed directly to step 5.
- Return to the article in Content Genius. After you receive confirmation that the lock has been cleared (or if it cleared on its own), navigate back to Content → Content Genius (What are we writing today?) and open the previously locked article.
- Retry your AI edit. Attempt the AI edit again. It should now proceed without errors. If the 409 error appears again, reply in the same support chat thread immediately — do not start a new conversation — so the agent can investigate further without losing context.
- Request a credit review in the same conversation. If the failed execution consumed AI premium quota, tell the support agent during the same conversation. Provide the article name and the approximate date and time the failure occurred. Our team can review your account and restore any credits lost due to the stuck process.
💡 Tips to Avoid This in the Future
- If an AI edit appears to be running for an unusually long time without completing, do not refresh the page repeatedly or navigate away and back in quick succession — allow it to finish or time out naturally first.
- If you must navigate away, wait at least 2–3 minutes before returning and retrying, so any in-flight server process has time to resolve or fail cleanly.
- If you see the 409 error immediately on your first attempt (not after a timeout), contact support right away rather than retrying multiple times.
If you are still experiencing this issue after following these steps, please reach out to our support team via the in-app chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.