Deployments
What starts a deployment, what the phases mean, and how to retry, redeploy or cancel one.
A deployment is one build-and-release of an application. SeneDx keeps the whole history: which commit, what was built, and what happened.
What starts a deployment
- A push to the tracked branch — automatic.
- Redeploy, from the dashboard: it releases a previous deployment's commit again.
- Retry, which runs a deployment that failed a second time.
The phases you will see
Queued, provisioning, building, deploying, then live. The panel shows the current phase and the log output as it arrives. A phase that runs past its budget is stopped by the platform and the reason is recorded, so a build that hangs cannot run for ever.
When a deployment fails
The message and the build output stay with the deployment. The message names the cause when we can identify it — a missing dependency, a failing build command, a type error — and it says so when it cannot.
Three actions on a deployment
- Retry — run the same deployment again.
- Redeploy — release an earlier deployment's commit again; this is also how you roll back a bad release.
- Cancel — stop a deployment that is still running.
Did this page help you?
If something here is wrong, missing or unclear, tell us and we will fix the page.
Contact support