Fixing the primaryapi_server_error Login Loop

primaryapi_server_error is currently blocking access for some users, often appearing right after a "Unable to load projects" warning.

If you're seeing this, clearing your browser cache usually doesn't fix it—in fact, some users report that clearing the cache is when the login failure actually starts. It persists even in incognito mode, which suggests the issue is server-side rather than a local browser glitch.

If you are stuck in this loop, try these steps:
1. Log out completely from all sessions.
2. Check the official status page to see if there's a widespread API outage.
3. Wait 15-30 minutes before attempting another login to avoid triggering rate limits during a server instability phase.

Since this looks like a backend authentication failure, there isn't much to do on the prompt engineering side; it's a waiting game for the infrastructure to stabilize.