1.0.0-rc.1 · Release Candidate1 min read
Recovery Decision Matrix
Choose retry, roll-forward, image rollback, or database restore using source-verified AutoCore conditions.
| Situation | First choice | Stop condition |
|---|---|---|
| Safe interrupted step with valid lock/backup state | Resume or retry | Unknown mutation or active concurrent process |
| Image pull or port failure before mutation | Correct host/artifact and rerun preflight | Unavailable authorized artifact |
| Service health failure with compatible schema | Diagnose or roll forward | Evidence of data corruption |
| Application defect after migration | Compatibility-reviewed image rollback or roll-forward | Previous image cannot read current schema |
| Migration failure | Preserve logs and backup; obtain database decision | Any attempt to force or reset migrations |
| Corrupt backup | Stop and create a new verified backup | No verified restore point |
| Confirmed unsafe database state | Approved restore and derived-state rebuild | Missing approval or uncertain data-loss boundary |
Destructive actions require approval
Database restore, volume removal, migration reset, and broad data deletion are not automatic recovery steps.
Verification
Record the selected decision, evidence preserved, action owner, expected state, and post-recovery acceptance result.
Related articles
Idempotent RetryRetry completed or interrupted AutoCore installer operations only where source evidence proves safe repeat behavior.Rollback PlanningDecide between roll-forward, application rollback, and database restore before changing an AutoCore release.Database Restore DecisionDecide whether a verified PostgreSQL restore is safer than retry, roll-forward, or image rollback.