Claim Troubleshooting¶
Common Symptoms¶
| Symptom | Likely cause | Check |
|---|---|---|
| claim initiation reverts | state not running or amount > claimable | inspect runningClaimableRewardsWei and claim state |
| claim finalization reverts at readiness | pending claim delay not met | compare readyAt vs current timestamp |
| executor rejected | grant missing/expired/paused | inspect executor grant and pause flag |
| claim canceled unexpectedly | risk/receipt/exit transition invalidated claim | inspect event timeline for risk updates or exits |
| settlement reward claim fails | no finalized settlement rewards available | inspect claimableSettlementRewardsWei |
Operator Checklist¶
- verify seat and vault are initialized and registered.
- inspect current risk state, dust state, and claim state.
- inspect pending claim status.
- inspect cap usage for beneficiary and executor.
- inspect recent receipt and risk-update events.
Operational Detail¶
Troubleshooting starts by classifying the blocker as authority, pending-delay, cap, stale-data, economic-bucket, settlement, or incident state. Fix the smallest failing layer and preserve evidence before retrying.
Required Checks¶
- Verify source manifest and generated inventory if the claim path changed.
- Read current risk observation, receipt ledger, reserve coverage, claim mode, pending claim, and gatekeeper caps.
- Confirm the caller is the beneficiary or an authorized executor for the required scope.
- Confirm no incident, stale oracle, slashing, exit, or settlement blocker changes the allowed path.
Failure Handling¶
A failed claim is not automatically a contract defect. Preserve revert data, current reads, and source evidence. Retry only after identifying whether the failure belongs to Upgrade governance, Deposit permissioning, Custody/readiness, or Economic/claim safety.
Retry Rule¶
Do not retry with a larger amount, different executor, or alternate destination merely to find a passing path. Recompute the expected authorized amount, caller scope, pending delay, and cap room first. A retry that changes more than one variable at a time destroys the evidence needed to diagnose the original failure.