Status reasons

Each reason below appears in apps deploys list and in the deploy gate timeline. List them with the status-reasons CLI command or GET /api/v1/status-reasons.

Reason	Stage	What it means	Next step
`AutoRolledBack`	rollback	The post-deploy watch tripped and the previous release was restored automatically.	Find out why the new release tripped the watch before deploying it again.
`Canceled`	queue	An operator canceled the deploy before it finished.	Nothing to fix. Deploy again when you are ready.
`DetectedByPoll`	queue	The deploy was started by the git poller because a webhook was missed.	Nothing to fix. Check git webhook delivery if this happens often.
`ExitedDuringReadiness`	gate	The new container exited before it became ready.	Read the app logs for the start-up error, fix it and redeploy.
`ExitedDuringStableWindow`	gate	The new container was ready but exited during the stability window.	Read the app logs for the crash cause, fix it and redeploy.
`Frozen`	queue	The deploy was held because a deploy freeze is active for this app.	Wait for the freeze to end, or approve the held deploy if you are allowed to override it.
`NoRollbackTarget`	rollback	The watch tripped but there was no earlier healthy release to go back to.	Fix the app and redeploy, or deploy a known good image by hand.
`OOMKilledDuringReadiness`	gate	The new container was killed for running out of memory before it became ready.	Raise the app memory limit or reduce start-up memory use, then redeploy.
`OOMKilledDuringStableWindow`	gate	The new container was ready but was killed for memory during the stability window.	Raise the app memory limit, then redeploy.
`OperatorRollback`	rollback	An operator rolled the app back to an earlier release.	Nothing to fix. Deploy again when the problem with the newer release is solved.
`PostDeployCrashloop`	watch	The live release started crash looping after cutover.	Read the app logs, fix the crash or roll back to the previous release.
`PostDeployErrorRate`	watch	The error rate of the live release crossed the post-deploy watch limit.	Check the app logs and recent changes, fix forward or roll back.
`PostDeployExited`	watch	The live release exited after cutover.	Read the app logs for the exit cause or roll back to the previous release.
`PostDeployLatencyRegression`	watch	Response time of the live release regressed past the post-deploy watch limit.	Compare latency with the previous release, fix forward or roll back.
`PostDeployOOMKilled`	watch	The live release was killed for memory after cutover.	Raise the app memory limit or roll back to the previous release.
`ReadinessFailed`	gate	The new container never passed its readiness probe. The old release keeps serving when the strategy allows it.	Check the probe path and port, then read the app logs and redeploy.
`RestartedDuringStableWindow`	gate	The new container restarted during the stability window, so it was not trusted with traffic.	Read the app logs for the restart cause, fix it and redeploy.
`StabilityGateTimeout`	gate	The stability gate did not finish inside its time limit.	Check that the app starts promptly and the probe responds, then redeploy.
`StaleCommit`	queue	The commit is older than what is already deployed, so it was skipped.	Nothing to fix. Push a new commit to move forward from here.
`Superseded`	queue	A newer deploy replaced this one before it went live.	Nothing to fix. The newer deploy carries the latest change.
`WatchStopped`	watch	An operator ended the post-deploy watch early.	Nothing to fix. Redeploy or restart the watch if you still want the safety net.

Last modified on November 6, 2026

Essentials

Deploying

Networking and multi-node

Databases and storage

CI/CD and automation

Security and access

Scale and operations

AI and agents

Templates and catalog

Migrate

Beta and experimental