Deploy, health & rollback
Follow the actual release that serves traffic.
Before deploying
- Sync the selected branch and check the runtime tools and named start settings.
- For Web, save the required environment and configure the application port and HTTP health path. Add a project domain only when you want managed Nginx/TLS routing; its DNS must be ready.
- For Worker, empty user ENV is allowed. Do not configure a Portal port or HTTP probe; the entry point must keep running.
Read Worker activation and rollback behavior
Build and inspect
Use named package scripts for Node/Bun. Skip Build skips only the build script, not dependency installation, start validation or configured health checks. Python/PHP/Compose preparation completes through the host helper. Inspect release events for the actual phase rather than treating a successful source preflight as an HTTP success.
Active revision and rollback
A newer synced commit can differ from the active release. Check the deployed revision and runtime logs. Rollback activates a retained release with its recorded runtime settings, including Node major. Older native dependency trees may be cleaned beyond the active and immediate rollback releases. Deployment logs explain failures; externally visible application health still needs verification.