Deployments

A deployment is one build and release of a service. Follow it in the dashboard or let your agent watch it, then act on the result.

How it works

Pre-built images skip the build step. Source builds typically take 3–7 minutes, and pre-built images 1–2 minutes.

Status	Meaning
queued	Waiting for a build worker
building	Building an image from source
deploying	Starting containers and running health checks
healthy	Running and passing health checks
failed	Build or startup failed; read the logs
cancelled	The deployment was cancelled
rolled_back	Replaced by a rollback deployment

Watch progress

Open the project in the Build dashboard, or ask your agent to check the deployment about once a minute until it finishes.

Open the URL

When the deployment is healthy, open the service URL. A newly healthy deployment can take up to 60 seconds to start serving traffic.

Read the logs if it failed

Failed deployments include recent logs that show the build or startup error.

You can also cancel a deployment, roll back, restart a service, or redeploy. Your agent uses the deployment reference for these.

Start with the deployment logs. Common causes are:

For persistent failures, see the troubleshooting guide.

Configure ports, resources, and health checks.

Ask your agent to ship and watch releases.