Troubleshooting

GitHub connection failsCopy Anchor Link

Check the stable HTTPS origin, App installation, selected repository and webhook delivery. Restart an expired setup flow in the same browser session. A successful connection test does not establish browser or model readiness.

Preview is missing or inconclusiveCopy Anchor Link

Check that GitHub exposes a ready preview associated with the exact PR head SHA. A URL in a PR comment alone is not proof. Review competing candidates, destination safety and the persisted wait deadline; see preview deployments.

Sign-in is blockedCopy Anchor Link

Check profile scope, permitted origin and the disposable credentials. The current worker supports a single origin and does not support arbitrary SSO or MFA. Avoid putting passwords in logs, PR comments or model prompts.

No result or an inconclusive resultCopy Anchor Link

Confirm QA policy, PR eligibility, model configuration and budgets. Check the exact tested SHA and private run evidence. /readyz only checks PostgreSQL connectivity. An inconclusive result is not a pass.

Report or evidence is unavailableCopy Anchor Link

Confirm the administrator session and current repository access; evidence may have expired. For publication failures, follow docs/reporting.md: an uncertain GitHub create operation must be reconciled before any manual retry to avoid duplicate reports. Never paste secrets or signed preview URLs into support records.