🔍 What This Article Covers
Some users encountered a persistent Workflow failed error when trying to generate articles in Content Genius. Even after clearing the browser cache, performing a hard refresh, or switching to an incognito window, the error continued to appear — and in some cases, the article page became permanently stuck in a loading or in-progress state.
This article explains what caused the issue, confirms it has been resolved, and tells you what to do if you are still experiencing it.
⚙️ What Caused the Issue
The root cause was a bug in the Content Genius article generation pipeline. When the background generation process failed partway through, the system did not correctly clean up the job. As a result, the article page remained stuck in an AI in progress state indefinitely, and new generation attempts continued to fail.
This was an internal platform-side issue — not caused by anything in your browser, account settings, or content inputs. Browser troubleshooting steps such as clearing cache or using incognito mode did not resolve it because the problem existed in the generation pipeline itself.
✅ The Fix Is Now Live
Search Atlas engineering identified and resolved this bug. The fix was reviewed, tested through quality assurance, and deployed to the platform. Articles that were stuck in a failed or in-progress state should now be recoverable, and new article generation attempts should complete successfully.
🚀 Steps to Try After the Fix
- Navigate to Content → Content Genius (What are we writing today?) in your Search Atlas account.
- Locate the article that was stuck or that previously returned a Workflow failed error.
- Attempt to generate or re-generate the article as you normally would.
- If the article is still showing an in-progress or failed state, try starting a new article to confirm whether generation is working on your account.
- If the new article generates successfully but the original stuck article does not recover, you may need to recreate that article from scratch.
- Try a different browser. If the error only appears in one browser, it is likely a local browser issue rather than a platform bug.
💡 When to Contact Support
If you are still seeing Workflow failed errors or articles stuck in a permanent loading state after following the steps above, the issue may need to be investigated by our team directly.
Before reaching out, capture a recording or screenshot of the error — this will speed up escalation to our engineering team.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.