Deployment lifecycle
Every application release creates a deployment entry. Use deployment history to distinguish a configuration change from the release produced by that change.
View deployment history
Open the application, then select Deployments. Each row shows an identifier when available, creation and update times, and the current state. Select a row for details and progress output.
Statuses
| Status | Meaning | What to do |
|---|---|---|
| Pending / In progress | The release is still being prepared or started | Keep the page open or return later and refresh |
| Live | The release completed and is serving according to the platform state | Test the application and review logs |
| Failed | The release did not complete | Read the final meaningful error and correct its cause |
| Inactive | The deployment is no longer the active release | Use it for history; verify the current live deployment |
Follow progress
The deployment details page shows the current state, timestamps, a run identifier when available, and progress output while the deployment is active. Output can pause temporarily even while work continues; use Refresh to update the recorded state.
Do not post deployment output publicly without reviewing it. Well-behaved applications should not log secrets, but logs can still contain customer data, internal paths, or sensitive request details.
After a live deployment
Complete a small release check:
- confirm this is the intended application and source version;
- open the public endpoint when present;
- test health and one important user path;
- check runtime logs for errors or repeated restarts;
- confirm dependent services behave normally;
- record the change according to your team’s release process.
Configuration saves and deployments
Saving any application settings section starts a new deployment. Make one coherent section change, save it, and verify that release before editing another section. This keeps the cause of a failure easier to identify.