Problem summary
Bold Create uses your Git provider integration to list repositories, clone them, push the agent’s branch, and open pull requests. If the access behind the integration stops working, these actions fail until you reconnect. You may see one of these:
- A thread or picker shows {Provider} OAuth token is invalid or has been revoked. Please reconnect the integration., for example GitHub OAuth token is invalid or has been revoked. Please reconnect the integration.
- The agent reports that The git provider rejected the credentials when it tries to push or open a pull request.
- The provider row on the Integrations page shows Connect instead of Connected.
- The repository picker is empty, or shows the hint Connect a Git provider to use this repository.
- An environment build fails because a repository could not be cloned.
Possible causes
- Access was revoked in the Git provider: you or an admin removed Bold Create from your authorized applications.
- The Gitea personal access token expired or was deleted.
- The integration was disconnected on the Integrations page.
- Your account lost access to the organization or repository, for example after a role change.
Resolution steps
Step 1: Reconnect the provider
- In the sidebar, select Integrations.
- Find the provider under Source Control.
- Reconnect it:
- GitHub or GitLab: select Connect, then Continue, and approve access in the provider. See Connect GitHub or Connect GitLab.
- Gitea: create a new personal access token in Gitea, select Connect, enter your server URL and the new token, and select Connect. See Connect Gitea. The new connection replaces the old one. A message such as GitHub connected successfully. appears, and the row shows Connected. If the row still shows Connected but threads report the token error, select Manage > Disconnect, then connect again.
Step 2: Check the connection
- In the sidebar, select New task.
- Select Repository or environment.
- Check that your repositories are listed under Repositories.
Step 3: Continue your work
- A thread that stopped with the error: open the thread and select Try Again on the error, or Retry on the last response. You can also send a follow-up message, for example Push the changes and open the pull request again. See Run stopped or shows Error.
- An environment build that failed: open the environment and select Rebuild. Builds clone repositories with the connection of the person who created the environment, so that person must reconnect first.
Access denied instead of token invalid
If the message is {Provider} denied access to this resource. Check that your token has the required scopes and that you have access to the organization or repository., the connection works but can’t reach this resource. Reconnecting alone may not help. Check that:
- Your account can open the repository in the Git provider.
- Your account has write access, if the agent needs to push or open a pull request.
- Your GitHub organization approved Bold Create, and you authorized it for SAML single sign-on if your organization uses it.
- Your Gitea token has the user and repository permissions described in Connect Gitea.
Rate limits are not token errors
{Provider} is temporarily unable to process your request due to rate limiting. Please try again in a few moments. means your Git provider is limiting requests. Your connection is still valid. Wait a few minutes and try again. Don’t reconnect.
Prevent this problem
- Gitea: set an expiry date you will remember, or use a token without an expiry if your policy allows it. Replace the token before it expires.
- GitHub and GitLab: don’t revoke Bold Create in your provider’s settings while you have threads or shared environments that use it.
- Shared environments: if you created environments your team uses, keep your connection active. Their builds use it.