Troubleshooting

Find the message you're seeing below. If it isn't here, ask the Help assistant in the console first: it can open a support ticket with your conversation attached.

Git connections

"Token rejected — check the URL and key." The Git host refused the token. Check that the instance URL is your server's base address, that the token hasn't expired, and that it has the scopes listed in the guide for your host: GitHub, GitLab, Bitbucket, Gitea, Forgejo.

"… sign-in isn't set up on this server" OAuth isn't available for that host or server. Connect with a personal access token instead.

"Use the public https address of your Git server" AI CodeOps runs in the cloud and can only reach Git servers on the public internet over https. Private addresses, localhost and URLs with a query string are refused.

A connection shows Active, but repositories fail to load The token may have been revoked on the Git host; the status only tracks the expiry date. Disconnect under Configure → Settings → Git Providers and connect again.

Sessions

"Connect a model provider to run this session" The workspace has no provider of its own and the platform's models aren't available to it. Add a provider key on the Dashboard under Bring Your Own Key, or contact support.

"… models aren't set up on this platform yet" That tier isn't offered right now. Start the session on Economy or Auto, or use your own provider key.

A session stopped because an allowance was used up The tier's monthly allowance ran out and the workspace has no credits. Use another tier, add credits on the Billing page, connect your own key, or wait for the reset on the 1st of the month (UTC). See Models and tiers.

"Over budget" or "Stopped over budget" The workspace budget, or the cap for that workflow, was reached. An owner, admin or billing admin can raise it under Configure → Billing → Cost budget. See Cost controls.

A session failed on a provider error If it ran on your own key, check that the key is valid and has quota with that provider.

"No projects yet — AI-generated code must live in a project." Create a project first under Plan → Projects. See Projects.

A session is waiting before it starts A workspace policy requires approval to start that workflow. It waits on Review & Gate → Approvals; if the approval is rejected or expires, the session is cancelled.

Pull requests

"This change is awaiting human approval." Approve it on Review & Gate → Approvals or with Accept changes on the session page. If you launched the session, someone else has to approve it.

"This change isn't release-ready: …" The quality gate found failing tests, open high or critical findings, or an AI review that didn't finish. Triage the findings or re-run the session. See Quality gates.

"This change was rejected in review" Start a follow-up from the session page to revise it.

"The release check couldn't run just now." A temporary problem. Try again in a moment.

The Create Pull Request button is locked The label says why: Connect git to open PR (connect an account for the repository's host) or Add a repository to open PR (add a repository URL to the project).

Access and sign-in

A page or button is missing Your role may not allow it. Ask a workspace owner or admin. See Members and roles.

"Someone else needs to approve a change from a session you launched." The two-person rule: another member who can approve has to decide.

An invitation link says it has expired or was already used Invitation links last 7 days and work once. Ask an admin to send a new one, and sign in with the address it was sent to.

Signed out unexpectedly Sign-ins expire after a while; sign in again. If your account was suspended, you'll see a notice.

SSO sign-in fails Your email domain must match the SSO connection's verified domain, and the connection must be active. Ask your administrator to check Configure → Settings → Single sign-on. See Single sign-on.

Still stuck?

Ask the Help assistant in the console, then choose Contact support. A support engineer replies by email and in the Help panel. You can also reach us through the contact page.