MultiConnectCloud › API Deployments
11. Update your API
From the dashboard, open your project, then the deployment, and click Update. The same steps as when you created it open, filled in with your current settings. Platform and Hosting Plan are shown but cannot be changed here: the platform is fixed, and the plan is changed from the deployment page (Section 12).
In the Build step, choose one:
| Option | What happens |
|---|---|
| Redeploy Existing Build | Your settings are saved. If you changed environment variables, the entry point, the start command or Web Socket, your current build is redeployed with them. Other changes, such as the name or autoscaling thresholds, are saved without a redeploy |
| Upload New Build | Choose a new zip. It is uploaded and deployed with your settings. Leave Rollback on failure on to keep the old build serving if the new one fails |
Click Submit. The messages you may see:
| Message | Meaning |
|---|---|
| Configuration saved. | Nothing needed a redeploy |
| Configuration saved. Redeploying with your current build. | A redeploy has started |
| Configuration saved. It will apply when you start the deployment. | The deployment is stopped. The change applies when you start it |
| Configuration saved. It will apply once the first deployment finishes. | The first deploy is still running |
| Redeploy queued. The current build keeps serving until the new containers are healthy. | Your new build is deploying |
Every new build gets a higher build number. The Containers section shows the Build Version each container runs.

