If you are using a context in your workflow, you may encounter the following message.
If your builds are failing as "Unauthorized" and you are utilizing contexts, please try the following troubleshooting steps:
- Restricted Contexts: If you are using a Restricted Context, confirm the blocked user is a part of the security group (defined by GitHub teams), users that are not a part of the GitHub team will not have access to the context
- Stale Permissions: If your permission level recently changed, please have an organization admin refresh your user permissions. Additionally, the user in question should also refresh their permissions. A user can refresh their permissions by navigating to their user settings page and click "Refresh Permissions."
- Nested Teams: If the context you are attempting to use is part of a nested team, you will need to add the nested team as a security group
- Account renames: If you recently renamed your GitHub username and are suddenly experiencing permission issues please contact Support
- Browser extensions: Try to disable browser extensions or log in from a different browser and/or device. If you are still blocked, please submit a HAR file to Support
- Invalid/Expired OAuth token: Proceed to a full re-authentication
- Recent change to Context Restrictions: If you've recently adjusted the permissions of a context, changes may not be available immediately due to caching. You will need an organization admin to refresh permissions at https://app.circleci.com/settings/user (more info)
- Project Restrictions: If your team utilizes project restrictions on Contexts, you may be trying to use the Context in a project that it is not authorized to be used in.
Please note that you can leverage the CircleCI v2 API to find the user id of a user who triggered a workflow. You can use the Get a workflow endpoint. The value assigned to
started_by key in the response corresponds to the user ID of the user who triggered the build.