Managing Deployments

Once your app is deployed, you can manage it from the Apps > Deployed tab.

The Deployed Tab

The deployed tab shows all active deployments with:

• Status indicator — Color-coded dot showing current state
• Name and app ID
• Image tag — The container image version
• Replicas — Ready/total instance count
• Hostname — The public URL
• Created date

Status Indicators

Status	Description
Running	App is live and healthy
Deploying	Starting up (animated indicator)
Updating	Rolling update in progress (animated)
Pending	Waiting for resources (animated)
Stopped	Manually stopped
Failed	Error occurred
Deleting	Being removed (animated)

The page auto-refreshes every 5 seconds when deployments are in a transient state (deploying, updating, pending, deleting).

Deployment Detail

Click a deployment to open its detail page. From here you can:

Update the Image

Enter a new image tag and click Update to trigger a rolling update.

Edit Configuration

Modify these settings and click Save Changes:

• Port and replicas
• Resource preset (Starter, Standard, Performance, Heavy, Custom)
• Access control — Auth mode and minimum role
• Allowed/denied users — Restrict access to specific members
• Environment variables — Add, edit, or remove variables

View Container Logs

Toggle the logs panel to see real-time container output. Choose the number of tail lines (100, 200, 500, or 1000) and click refresh to get the latest logs.

TIP

Container logs show real-time output from the running container.

Run Diagnostics

Open the Diagnostics tab on a deployment to inspect runtime health and recent platform events. Diagnostics are useful when a deployment is stuck in Failed, Pending, or Deploying, or when the app is live but not behaving as expected.

See Diagnostics for the full workflow.

Deployment Lifecycle

Action	Effect
Start	Resumes a stopped deployment
Stop	Gracefully stops all replicas
Redeploy	Restarts with the current configuration
Delete	Permanently removes the deployment (requires confirmation)

Troubleshooting

Symptom	What to check
Deployment stays Pending	Check resource requests, quotas, and whether the selected image can be pulled.
Deployment enters Failed	Open logs first, then run diagnostics for platform-level context.
App URL returns 401	Review access control and confirm the caller has the required role or token.
App URL returns 502/503	Confirm the container listens on the configured port and has at least one ready replica.
Update does not appear	Verify the image tag changed, then use Redeploy if the same tag was reused.

Next Steps

• Configure access control for your deployments
• Provision storage for your applications
• Run diagnostics when a deployment is unhealthy