MultiConnectCloud › API Deployments
10. How a deploy runs
Every change that starts new containers runs as an operation you can watch on the deployment page. That includes the first deploy, a new build, a settings change, a plan change and scaling.
| Stage | What is happening |
|---|---|
| Provisioning | New containers are being created with the new build or settings |
| Awaiting healthy | The new containers must answer GET /health with a 2xx |
| Switching | Traffic moves to the new containers |
| Draining | The old containers finish their requests and are removed |
| Completed | The change is live |
| Rolled back | The new containers never became healthy. The previous build is still serving and nothing changed for your callers |
One operation runs at a time per deployment. While one is running, the other actions are unavailable.
Rolling back
- Automatically. When you upload a new build, Rollback on failure is on by default: if the new build never becomes healthy, the previous one keeps serving. Settings changes, database links and plan changes roll back the same way.
- To an older build. There is no button to go back to an earlier build. Upload that build again as a new build.

