Deploy states and phases

These are the phase names shown on deploy records; the lifecycle behind them is explained in How deploys move from code to traffic.

Active deploy phases

Phase	Meaning
Pending	The operation is waiting to start.
Validating	synsmarts is checking the revision and App configuration.
Classifying	synsmarts is determining whether Magento database changes are code-only, additive, breaking, or unknown.
Building	The runnable release is being prepared.
Migrating	Required database changes are being applied.
Rendering	The target App configuration is being prepared.
Deploying	The replacement release is starting.
Promoting	Health checks passed and traffic is moving to the replacement.
Cleaning up	Temporary release resources are being removed.

Not every deploy displays every phase. A code-only release can skip migration. WordPress deploys use the code-only path. Magento classification can continue after the image build when synsmarts must compare the serving and candidate schema inventories.

Terminal outcomes

Outcome	Meaning
Complete	The intended release is serving.
Failed	The operation stopped without reaching its intended result.
Restore failed	Recovery after a data-changing failure didn’t complete; contact support.
Cancelled	The operation was intentionally stopped before completion.
Superseded	A newer accepted operation replaced this one.

The portal can display Complete while internal cleanup is still being reconciled. The customer-visible result remains successful because the intended release is serving.

Rollback decision state

Awaiting approval isn’t a normal deploy phase. It appears when a rollback that can affect data is waiting for an explicit customer decision.

Rollback availability isn’t determined by phase alone. The portal also checks the previous release, the type of change, and whether a safe rollback path exists.