What are the status values for deployments and operations?

What is the deployment status lifecycle?

What are terminal vs non-terminal operation statuses?

How do deployment phases map to statuses?

Status Model

This page documents the status model for deployments and operations.

Deployment Status

Deployments have the following statuses:

Status	Description
`provisioning`	Deployment is being created
`ready`	Deployment is ready and accessible
`destroying`	Deployment is being destroyed
`failed`	Deployment failed (cannot be recovered)
`destroyed`	Deployment has been destroyed

Status Flow

Deployments progress from provisioning to ready. If provisioning fails, the status becomes failed. From ready, deployments can transition to destroying and then destroyed.

Operation Status

Operations have the following statuses:

Status	Description
`queued`	Operation is queued and waiting to start
`running`	Operation is currently executing
`succeeded`	Operation completed successfully
`failed`	Operation failed
`canceled`	Operation was canceled

Terminal States

These states indicate the operation will not change:

succeeded
failed
canceled

Non-Terminal States

These states indicate the operation is still in progress:

queued
running

Status Mapping

Deployment Phases

Deployments progress through phases that map to public statuses:

Deployment Phase	Public Status
Initialization	`provisioning`
Database provisioning	`provisioning`
Infrastructure provisioning	`provisioning`
Application bootstrap	`provisioning`
Subdomain configuration	`provisioning`
Ready	`ready`
Destroying	`destroying`
Destroyed	`destroyed`
Failed	`failed`