Execution Status
The recovery system uses two layers of status: step-level statuses describe each operation, while task-level outcomes explain how to understand the entire recovery run and what to do next.
Task-Level Outcomes
| Outcome | Meaning | Recommended Action |
|---|---|---|
| completed | This run produced actual progress or recovered funds, and no immediate rerun is needed | No immediate rerun needed |
| partial | This run only partially progressed, or recovered nothing while assets still remain blocked/waiting | Review the summary and follow up as needed |
| waiting_to_rerun | This run progressed successfully, but protocol waiting or lock windows remain | Rerun after the waiting window ends |
| failed | This run was interrupted by a fatal error | Fix the root cause before retrying |
Step-Level Statuses
Status Matrix
| Status | Icon | Meaning | Recommended Action |
|---|---|---|---|
| completed | ✅ | Step fully completed | Wait for next steps |
| completed_partial | ⚠️ | Partial success, some assets skipped or failed | Review notes and rerun if needed |
| completed_waiting | ⏰ | Operation succeeded but protocol waiting period applies | Rerun at suggested time |
| skipped_locked | 🔒 | Assets currently locked | Wait for unlock and rerun |
| skipped_no_assets | ➖ | No eligible assets for this step | No action required |
| failed_system_error | ❌ | System-level failure | Retry later or contact support |
| failed_user_error | ⛔ | Input or configuration issue | Fix input and retry |
| failed_network_error | 🌐❌ | Network or RPC issue | Check network and retry |
Typical Interpretations
⚠️ completed_partial: common when only part of vault/staking assets are currently executable.⏰ completed_waiting: common in staking, where execution succeeds but unlock windows remain (for example, 1-day or 7-day waiting periods).🔒 skipped_locked: not a hard failure; it indicates protocol lock state.- If the whole run is only
skipped_*and no funds are actually recovered, the task-level outcome becomespartial, notcompleted.
When to Rerun Recovery
- If the task-level outcome is
waiting_to_rerun, rerun after the suggested unlock time. - If the task-level outcome is
completed, no immediate extra action is usually required. - If the task-level outcome is
partial, review the remaining issues before deciding whether to rerun now. - If step outputs include
failed_*and the task-level outcome isfailed, resolve the root cause first, then rerun.
