Observe and troubleshoot

Check status first

Start with resource, deployment, runtime, proxy, and access route status before assuming the whole deployment failed.

Runtime logs

Runtime logs come from application stdout/stderr and help identify startup, port, configuration, and runtime failures.

Health summary

The health summary combines deployment, runtime, health policy, proxy, and public access observations.

Copy diagnostic summary

Diagnostic summaries should include stable IDs, status, error codes, and safe context while masking secrets.

Safe recovery

Prefer retryable operations first. Change server, credential, proxy, or domain configuration only when the status explains why.