Read install, build, and release logs
Inspect preparation failures before changing a running app.
Run locally and choose the logs for your deployment strategy.
Use the release ID returned by the deployment or list command. Preparation failures can happen before activation; inspect status rather than assuming the active app was replaced.
This selects the application’s install log source rather than runtime output. CLI tools may have install logs without a long-running service.
Use the build identifier reported by the deployment or build list. Check dependency installation, command exit status, disk space, and runtime availability. Incremental installation is unprivileged; system package installation belongs in the workspace image path.