Troubleshooting
Start with the failing boundary and gather a small, useful diagnostic record.
Check context and health#
Confirm the selected environment before investigating a missing service. Then inspect resource health and the most recent deployment events. A successful apply means the desired state was accepted; readiness may still be converging.
du context show
du doctor
du services describe catalog
du events list --service catalog --since 30mCommon symptoms#
| Symptom | Check first |
|---|---|
| Service remains pending | Capacity availability and placement constraints |
| Gateway returns 503 | Service readiness and healthy replica count |
| API returns 403 | Identity scopes and project membership |
| A change is not visible | Active context and deployed revision |
| Volume attachment fails | Region, access mode, and current attachment |
Collect a safe support bundle#
Record the request ID, resource name, environment, and approximate event time. Redact credentials and customer content. A useful report includes expected behavior, actual behavior, and the smallest reproduction you can provide.