// DEPLOYMENTS
Roll Back a Deployment
Redeploy a previous image without rebuilding.
Rollback creates a new deploy that reuses a previous deploy's already-built image (imageTag) instead of rebuilding from source. That makes it fast — seconds, not a full build cycle — and it's the safest way to recover from a bad release.
It only works if the target deploy still has an image on disk. A background job keeps only the 5 most recent images per project (plus whichever is currently active) and prunes the rest to save disk space, so rollback is realistically limited to your recent deploy history, not an arbitrary point in the past.