Operator Troubleshooting
Common failure classes
Permission denied
Role mismatch or missing hat assignment blocks create/review operations.
Confirm wallet/account role on the active chain and garden.
Route exists but action fails
On Arbitrum the v1 modules are deployed, so start with roles, inputs, and the selected chain. On other networks some modules may still be zero-address.
Check packages/contracts/deployments/*-latest.json and packages/indexer/config.yaml before treating as runtime bug.
Indexer mismatch
Vault activity is indexed on Arbitrum through dynamic vault registration, so a wrong balance is more likely indexer sync lag than missing coverage. Cookie jar per-jar deposit and withdrawal activity is not indexed and will not appear regardless of sync.
Check indexer sync lag and dynamic vault registration first, then compare deployed addresses and indexer network config before assuming a runtime bug.
Escalation packet
Share these in incident reports:
- Chain ID and garden address.
- Route and exact action attempted.
- Transaction hash (if any).
- Console/network error snippet.
- Deployment/indexer address check results.
Next page
Next best action
Confirm whether the issue is activation-state drift before opening a bug.
Check deployment status