Deployment ties

A Deployment ties your Service configuration to what runs on compute. Start with Logs and debugging so you know which log surface to open.

Build fails (compile, install, or image pull)

1. Open Deployments for the Service and read the build log. Copy the first error block (no secrets).
2. Git-backed Services: fix the branch, Dockerfile path, or build command the repo expects. Check App services under Services in the sidebar.
3. Docker Services: confirm image tag, platform, and registry credentials. See Docker services under Services in the sidebar and Integration issues.
4. Dependency or lockfile errors: reproduce locally with the same commit when possible.

Task guides: Redeploy and rollback under Deployments and Operations in the sidebar, Logs under Deployments and Operations in the sidebar.

Deploy hangs, stays queued, or repeats

1. Check Worker Node health and connection messages on the Environment. See Compute and worker node issues.
2. Look for concurrent operations (another deploy or scaling change) in Health checks and runtime behavior under Deployments and Operations in the sidebar.
3. If the UI disables actions briefly after variable or config changes, wait for reconciliation, then retry Deploy or Redeploy.

Service crashes or restarts right after deploy

1. Read runtime logs for stack traces or exit codes.
2. Confirm environment variables are set and that you redeployed after changes. See Environment variable issues.
3. Verify health check paths and ports match what the app listens on (Health checks and runtime behavior under Deployments and Operations in the sidebar).
4. Database connection errors: confirm connection strings and internal hostnames; see Database services under Services in the sidebar and Database troubleshooting under Databases in the sidebar.

Wrong release or need to go back

Use Redeploy and rollback under Deployments and Operations in the sidebar. Prefer rolling forward with a known good commit when rollback UI is limited.

Database Service deploy or provision fails

1. Treat the Deployment log like any other Service: read the failure reason first.
2. Check Environment compute and disk; database Services need stable storage and resources.
3. Deeper engine-specific notes: Databases overview under Databases in the sidebar and Database troubleshooting under Databases in the sidebar.

Domains or routing look wrong after deploy

TLS and hostname issues are usually Domain and SSL issues and Domains and SSL under Deployments and Operations in the sidebar, not a failed deploy.

Related

• Troubleshooting overview
• Deployments overview
• Operational best practices