"Something Unexpected Happened" error

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.

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)