Skip to main content

Locate the failure

Run locally:
Check whether the failure happened before submission, during preparation, or during activation. Read the original command’s error and release logs.

Common causes

Retry safely

Fix one identified cause, then repeat the same deployment against its intended target. Keep .rig.lock unless you deliberately intend to change the deployment identity. Check the latest release before attempting activation again. Use deployment strategies for an older project and app rollback for retained code/configuration. Neither is a substitute for a data restore.