Overview
The "Something Unexpected Happened" error is a generic UI message that can appear in several different contexts on CircleCI. This article covers the most common causes and how to resolve each one.
Common Causes
1. Insufficient permissions to access Organization Settings
Symptom: You see this error (often accompanied by a 404) when navigating to your organization's settings page.
Cause: Certain organization settings in CircleCI are restricted to org admins. If your account does not have admin-level permissions, you will be blocked from viewing these pages.
Resolution:
Confirm your role in the CircleCI organization. Navigate to Organization Settings > People and verify that your account is listed as an Admin.
If you are not an admin, ask an existing org admin to either grant you admin permissions or access the settings on your behalf.
If you believe you should have admin access, try refreshing your permissions or performing a full re-authentication.
For more detail on what permissions are required for the GitHub OAuth integration, see the GitHub OAuth permissions overview in the CircleCI docs.
2. SSO / SAML configuration issue
Symptom: You see this error during SSO setup or when logging in via SAML.
Cause: A misconfiguration in your SSO/SAML settings can cause authentication to fail and surface this generic error message.
Resolution: See the dedicated article: Resolving "Something Unexpected Happened" Error in CircleCI SSO Configuration.
3. GitHub OAuth permissions issue
Symptom: You see this error after connecting CircleCI to a GitHub organization, or when accessing a project or pipeline for the first time.
Cause: CircleCI may not have been granted access to the GitHub organization, or third-party app restrictions may be blocking the OAuth app.
Resolution:
Navigate to the CircleCI OAuth App in your GitHub account settings.
Under Organization Access, grant or request access for your organization.
Ensure CircleCI is permitted under your organization's Third-party application access policy.
If the issue persists, try performing a re-authentication.
4. Oversized browser cookies (HTTP 431)
Symptom: You see this error on pages such as Pipelines, Insights, or when running actions in the web app. A refresh does not help.
How to confirm:
Open Developer Tools (Chrome / Edge: Cmd + Option + I on Mac, or F12 / Ctrl + Shift + I on Windows).
Open the Network tab and reload the page that shows the error.
Look for failed requests with status 431, or a response body that includes Request Header Fields Too Large. These often appear on API calls such as
/api/v3/orgsor/api/v3/projects.
Cause: Your browser is sending too many or too-large cookies for circleci.com / app.circleci.com. The request headers exceed the size the server accepts, so the page fails and shows the generic error.
Resolution: Clear CircleCI cookies for your browser profile, then sign in again:
Go to https://app.circleci.com.
Open Developer Tools (Cmd + Option + I on Mac, or F12 / Ctrl + Shift + I on Windows).
Open the Application tab (Chrome / Edge). In Firefox, use Storage.
In the left sidebar, expand Cookies.
Select
https://app.circleci.comand clear all cookies for that site (clear icon, or delete each cookie).If
https://circleci.comis listed separately under Cookies, clear those cookies too.Refresh the page, sign back in, and open the page that was failing.
If the error continues after clearing cookies, open a support ticket and include a HAR file captured while the error is showing, plus a screenshot of the Network tab showing the 431 responses.
Still seeing the error?
If none of the above resolves your issue, please open a support ticket and include:
The URL or page where the error appears
A screenshot of the error if possible
Your organization name and VCS provider (GitHub / Bitbucket / GitLab)
If the Network tab shows 431 responses, a HAR file from that session
