View deployments and logs

Deployment logs help diagnose image retrieval, build, and startup work. Runtime logs show application output after the container starts. Use both when a deployment request succeeds but the application is unavailable.

Inspect a deploymentCopy Anchor Link

1. Open the container and select Deployments.
2. Select a deployment to inspect its status, creation time, and log output.
3. Use Refresh to retrieve updated output. Use the pagination controls for older deployments.
4. Copy the logs when needed for investigation, after removing secrets before sharing them.

Some resources do not support deployment history. Missing or unavailable output is not evidence that a deployment completed successfully.

Deployment logs display some platform implementation details as ****. Surrounding progress messages and error diagnostics remain available. This masking does not remove all credentials or application secrets; review logs before sharing them.

Inspect runtime outputCopy Anchor Link

Recover an application that keeps restartingCopy Anchor Link

For an application in a restart loop, correct its settings or environment variables and save the changes. Return to Overview, select Redeploy, and confirm. Redeploy remains available while the runtime status is Restarting; you do not need to wait for the container to become healthy or make another settings change to enable it.

Redeploy requires deployment permission and saved or discarded drafts. It remains unavailable during an active resource operation, provisioning, or another pending change request. An accepted redeploy request does not mean recovery has completed; check Deployments and Runtime Log for the result.

Read application outputCopy Anchor Link

1. Select Runtime Log.
2. Adjust Maximum lines and the timestamp setting as needed.
3. Enable Live updates to receive new output as it arrives. Follow latest logs keeps the newest output visible; Wrap lines makes long messages easier to read.
4. Disable Live updates when examining a specific section of output. The displayed logs remain available; use Refresh for a new snapshot or enable live updates to reconnect.

Available startup and crash output can be viewed while a container is restarting or stopped. During a temporary connection failure, the last received logs remain visible while the viewer reconnects. A replacement container starts a fresh recent-log view; this page is not a permanent log archive. The viewer retains up to the selected number of lines, subject to a text-size limit.

If live updates cannot connect, try Refresh to retrieve a snapshot. Both methods read the same container output, including available logs while it is restarting or stopped. If the server cannot be reached, both methods can fail. If no output appears, check that the application writes to standard output or standard error. Files written only inside the container are not included. If log retrieval continues to fail, contact support with the resource ID and displayed error.

Information to include in a support requestCopy Anchor Link

Record the resource ID, deployment ID when available, approximate failure time, status, and relevant error output. Do not include credentials or environment-variable secrets.