Skip to main content
Start with the resource that failed: workspace, install/build, release activation, running app, or external access. A successful workspace boot does not prove the app is healthy; a healthy app does not prove its URL is public.

Collect a useful report

Record rig --version, the workspace/app/release IDs, the failing command, and the relevant error. Use --verbose for CLI diagnostics. Remove credentials and application secrets before sharing logs or traces. Inspect the current state before retrying. Avoid deleting workspaces, removing lock files, or opting into re-image as generic fixes; those actions can change the target or discard data.