This article addresses the 'failed to fetch' error that appears when working with the AI agent inside Content Genius — specifically when the agent fails to respond or load results regardless of what you type. This error is a connection-level failure, not a problem with your input, and it has specific causes and fixes you can work through step by step.
🔍 Common Causes
- Browser or network interruption: The AI agent loses its connection mid-session, often due to a timeout, unstable Wi-Fi, or a VPN interfering with requests.
- Stale session or cached data: An expired session token or corrupted cache can block the agent from making successful API calls.
- Browser extension conflict: Ad blockers, privacy extensions, or script blockers frequently intercept AI agent fetch requests.
- Temporary platform instability: A brief backend outage or degraded service can produce this error across all users intermittently.
📍 Where to Find It
The AI agent is accessed via Left sidebar → Home (Hi, CSM. What will we get done today?). Once there, click Launch Atlas Agent as a per-project action to open the agent interface where the error appears.
🛠️ Step-by-Step
- Reload the page: Press Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac) to do a hard refresh, bypassing the cache. Then relaunch the agent via Left sidebar → Home (Hi, CSM. What will we get done today?) → Launch Atlas Agent (per-project action).
- Check your internet connection: Open another tab and load a different website to confirm your connection is stable. If you are on Wi-Fi, try switching to a wired connection or a mobile hotspot to rule out network instability.
- Disable browser extensions: Open an Incognito or Private window (which disables most extensions by default) and navigate back to Left sidebar → Home (Hi, CSM. What will we get done today?) to test whether the error persists. If the agent works in Incognito, a browser extension is the cause — disable them one by one to identify the culprit.
- Clear browser cache and cookies: In your browser settings, clear cached images, files, and cookies for the Search Atlas domain, then log back in and retry the agent.
- Try a different browser: If the error continues, open Search Atlas in a different browser (e.g., switch from Chrome to Firefox or Edge) and relaunch the agent to isolate whether the issue is browser-specific.
- Disable your VPN (if applicable): If you are using a VPN, temporarily disconnect it and retry. VPNs can route traffic in ways that block AI agent fetch requests.
- Wait and retry: If none of the above steps resolve the issue, wait 5–10 minutes and try again, as this error can also be caused by a temporary platform-side issue that resolves on its own.
✅ How to Confirm It Worked
After applying any of the steps above, confirm the fix by doing the following:
- Navigate to Left sidebar → Home (Hi, CSM. What will we get done today?) and click Launch Atlas Agent (per-project action).
- Type any prompt into the agent input field and submit it.
- A successful connection will show the agent actively processing your request — you will see a loading indicator followed by a response, not the 'failed to fetch' error message.
- If the agent responds — even partially — the connection has been restored. If the error reappears immediately, note the exact steps you already tried and contact support using the method below.
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.