Troubleshooting

Start by checking the deployment host, account, repository, and client version. A feature may be present in source but disabled or not yet offered on your deployment. Use the visible error and your administrator's enabled-feature information to choose the next step.

Sign-in or repository access

Confirm that you signed into the intended host and account. Complete any required two-factor or organization sign-in step. A private repository you cannot access may appear not found; this does not prove it was deleted. Ask its owner to check your membership and permission.

For password recovery problems, use Account security. Do not send reset links, verification codes, or recovery codes to support.

Git clone or push

Copy the clone address from the repository. Confirm whether it uses HTTPS or SSH and configure the matching credential method. gbb auth status checks the CLI account; gbb auth setup-git explains its Git credential setup.

If cloning works but pushing fails, check write permission and protected-branch rules. Push your change to an allowed branch and open a pull request when required. A network timeout during push does not establish whether the remote accepted it; inspect the remote branch before repeating the operation.

API requests

Check the method, encoded path, request body, token scopes, and current resource permission against the API endpoint reference. A bearer token does not override repository or organization policy.

Respect any retry delay returned by the server. After a mutation loses its response, determine whether it was applied before sending a new logical request. Pagination differs by endpoint; use the fields declared for that operation rather than assuming every list is cursor-based.

Workflows and releases

A workflow that validates can still lack an eligible execution capability. Read the run's status and available logs, then confirm the enabled runner features with your administrator. See Actions.

If release creation is unavailable, confirm that release management is enabled and you have write permission. Publication requires an existing tag and a stable target. See Releases.

Client or device connections

Record the operating system, architecture, client version, intended host, approximate time, and displayed error. Follow the approved release or test channel's instructions. Do not install an unrelated build or grant broader device access just to bypass a connection failure.

Prepare a useful support request

Include what you tried, what you expected, what happened, and whether the problem repeats. Share a request or delivery identifier if one is shown, plus redacted error text. Remove credentials, cookies, reset links, customer data, and private repository or design contents from screenshots and logs. Send sensitive reports through your deployment's approved private support or security path.