Troubleshooting
| Symptom | What it usually means | What to do |
|---|---|---|
| Status shows "0 done today" but work clearly finished | A status service is running older code | An admin restarts the service: Restarting a service. Then re-check. |
| An agent says a number is "HELD" or "0 readiness" | That capability is intentionally gated until you act | Use the action/button next to it (e.g., add a key, request authority). Honest numbers are by design. |
| Memory/answers seem out of date | A service may need a restart, or ingestion is catching up | Restart the relevant Brain service; if it persists, contact Support. |
L1-L5 shows insufficient or stale coverage | The counter snapshot no longer matches active memory coverage | Ask an admin to regenerate L1-L5 counters and re-run /l1l5/status. |
A signed manifest says authority_grants=false | Correct behavior | Pointer manifests prove provenance; they do not grant authority by themselves. |
| A request was refused | It hit a safety/approval gate (credentials, identity, destructive, billing) | These require your explicit approval — confirm if you intend it. |
| Service won't come back after a restart | A deeper issue | Capture the on-screen output and the receipt path, then see Support. |
Before contacting support
Collect: what you did, what you expected, what happened, and any receipt path or error text shown. That makes resolution fast.