Troubleshooting
Start from a Lifecycle symptom and open the guide for the failed phase with safe evidence and recovery steps.
Start with the user-visible symptom. Before you know which phase failed, do not make broad cluster changes. Do not start another redeploy, edit the database, or dump secrets.
| Symptom | First check | Guide |
|---|---|---|
| No Lifecycle comment on a pull request | GitHub App access and repository onboarding | Missing pull-request comment |
| Environment shows Config error | Repository configuration validation | Failed deployment |
| Service shows Build failed | Console → Build | Failed build |
| Service shows Deploy failed or does not become Ready | Console → Deploy, then Pods | Failed deployment |
| Environment remains queued or stale | Last update time and if other work progresses | Stuck Environment |
| Cannot sign in, link GitHub, or call an API | Identity, key prefix, scopes, and request ID | Access and API errors |
| MCP, Agent workspace, or Site feature is missing | Feature availability and administrator policy | The feature’s availability section |
Safe escalation bundle
Collect:
- Lifecycle component and version
- Environment ID and Service name
- current status and status message
- source repository, branch, and short SHA when they are not private
- job name, phase, and timestamps
- request or correlation ID
- the smallest related, redacted log excerpt
Do not include access tokens, one-time API keys, OAuth callback query strings, Secret values, full Environment-variable dumps, private repository contents, or unredacted Agent conversations.