Overview
When using Atlas Agent inside Content Genius, you may encounter a "Request failed: 400" error. This can occur during various content workflows. Because the root cause of this error requires investigation on the backend, our support team will need to look into your specific case to identify and resolve it.
What Is Happening
A 400 error from Atlas Agent indicates that a request was rejected or could not be processed. The underlying reason can vary and is not always visible from the platform interface. This is a known error type that our team investigates on a case-by-case basis.
What to Try While You Wait
- Refresh the page. Reload Content Genius and attempt your action again — a fresh page load can sometimes clear transient errors.
- Try a different browser or incognito window. Open the platform in a private/incognito window or a different browser to rule out browser-specific issues.
- Clear your browser cache. Outdated cached data can occasionally interfere with platform requests. Clear your cache, then reload and try again.
What to Have Ready When You Contact Support
To help our team investigate as quickly as possible, please have the following information ready before reaching out:
- The exact error message you see (e.g. "Request failed: 400")
- The name of the article or project you were working on in Content Genius
- The specific action you were performing when the error appeared
- The approximate date and time the error occurred (including your timezone)
- Any steps you already tried to resolve it
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.