🔍 Overview
Some users experienced two related issues in Content Genius: a 400 error appearing when opening or posting to an article, and the tool becoming stuck in the research phase during article generation. Both issues were caused by a broken SQL join in the platform's backend (linked to an internal database inconsistency) and have since been fully resolved with a fix deployed to production.
If you encountered these errors before the fix was released, this article explains what happened, confirms the resolution, and tells you what to do if you are still seeing any issues.
⚠️ What the Errors Looked Like
- Opening a Content Genius article returned a 400 error (sometimes displayed via Cloudflare).
- The article generation process appeared to freeze or hang indefinitely in the research phase without progressing.
- Attempts to interact with the Content Genius agent returned a "Request failed: 400" message.
- Editing sessions timed out while generating article content.
🧩 Root Cause
Our engineering team identified a broken SQL join on a non-existent database reference within Content Genius. This caused the platform to fail when trying to load or process certain articles, resulting in 400 errors across multiple parts of the tool — including article opening, agent interactions, and the content generation workflow.
✅ Current Status: Resolved
The engineering team developed, reviewed, tested, and deployed a fix to production. Both the article 400 error and the research phase timeout are now resolved. You should be able to:
- Open existing Content Genius articles without errors.
- Generate new articles through Left sidebar → Content → Content Genius without the research phase freezing.
- Interact with the Content Genius agent without receiving 400 error messages.
🚀 Steps to Verify the Fix on Your Account
- Log out of Search Atlas and log back in to ensure you have a fresh session.
- Navigate to Left sidebar → Content → Content Genius.
- Open an existing article or start a new one using the available generation options.
- Allow the research phase to run. It should now progress normally without freezing or returning an error.
- If you were previously posting content to your site and received a 400 error, try the action again to confirm it completes successfully.
💡 If You Are Still Seeing Errors
The fix has been deployed and confirmed in production. However, if you are still experiencing 400 errors or a frozen research phase after following the steps above, here is what to try:
- Clear your browser cache and reload the page, or try an incognito/private browsing window.
- Try a different browser to rule out a local caching issue.
- Check that you are working with a newly started session rather than a tab left open from before the fix was deployed.
If none of the above resolves the issue, it is possible there is a separate edge case affecting your specific account or article. Please reach out so our team can investigate directly.
📋 Notes on Trial Extensions
If your trial period was impacted by these errors and you were unable to use Content Genius as expected, our team can review your account and apply an extension where appropriate. Raise this when you contact support and include the dates during which you were affected.
💬 Still Need Help?
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.