Each function can have many deployments, which can be thought of as versions of the mini-application. Functions can be created and deployed in different ways to meet your unique development habits.
Deployment status
Throughout the life cycle of a deployment, it could have the following status.
| Status | description |
| active | The deployment is built and currently activated and ready to be executed. A function can have one active deployment and deployment a must be active before being executed. |
| ready | A deployment is built, but is not activated. ready deployments can be activated to replace the current active deployment. |
| building | A deployment is being built. Check the build log for more detailed logs. |
| processing | The function deployment has begun and has not finished. |
| waiting | The deployment is queued but has not been picked up for processing. |
| failed | A deployment was not successful. Check the build log for detailed logs for debugging. |
Update deployment
Some Function settings require redeploying your function to be reflected in your active deployment. When you update a function by changing it's Git settings, Build settings, and Environment variables, you need to redeploy your function before they take effect.
Build logs
When you build a deployment, the logs generated will be saved for debugging purposes. You can find build logs by navigating to the deployments tab of your function, clicking the three-dots menu beside, and click Logs.
Redeploy
After updating the configuration, redeploy your function for changes to take effect. You can also redeploy to retry failed builds.
Navigate to Functions.
Open the function you wish to inspect.
Under the Deployments tab, find the status of the current active deployment.
Redeploy by clicking the triple-dots beside an execution, and hitting the Redeploy button.
Redeployment behavior varies depending on how the initial deployment was created.