Diagnostics

Diagnostics help you investigate deployments that are unhealthy, stuck, or behaving unexpectedly. The platform inspects deployment metadata and runtime health signals, then produces a human-readable report.

When to Use Diagnostics

Run diagnostics when:

• A deployment stays in Deploying, Pending, or Failed.
• The public URL returns 502 or 503.
• Replicas are not becoming ready.
• Logs are inconclusive.
• You need a quick summary before escalating to support.

Running a Diagnostic

1. Open Apps > Deployed.
2. Select the deployment.
3. Open the Diagnostics tab.
4. Click Run Diagnostic.
5. Review the generated report.

Diagnostics require deployment read access. If the button is not available, check your organization role and project membership.

What the Report Checks

The report can include:

• Deployment status and rollout state.
• Replica readiness.
• Runtime status and recent platform events.
• Routing configuration.
• Resource quota pressure.
• Recent logs and likely failure causes.

The report is scoped to the deployment and project visibility rules. It should not expose unrelated tenant resources.

Reading Results

Start with the first failed or warning section. Common patterns:

Finding	Likely cause
Image pull failure	Wrong tag, private registry credentials, or deleted image.
Crash loop	App exits on startup. Check container logs and required environment variables.
Readiness probe failure	App is running but not accepting traffic on the configured port.
No ready replicas	The app has no healthy instances available to receive traffic.
Routing error	DNS, TLS, or backend routing issue.

Escalating to Support

When you contact support, include:

• Organization slug.
• Project slug if relevant.
• Deployment name.
• Timestamp of the diagnostic.
• The error or warning section from the report.

Do not send secrets, tokens, or private keys. Redact application logs if they contain sensitive values.

Troubleshooting

Symptom	What to check
Diagnostic fails to start	Confirm diagnostics are available from Support & Status.
Report says deployment is not visible	Check project membership and deployment access rules.
Report times out	Retry once. If it repeats, check service status and contact support.
Report is clean but app fails	Check application-level logs, health endpoints, and external dependencies.

Next Steps

• Manage deployments
• Configure access control
• Contact support