HSX_E_DEV_MANAGED_LOGS
Managed dev logs unavailable.
What this error means
The managed session event stream could not be read or followed.
When this error stops a command, hs-x exits with code 1. With --json, the failure is reported as a structured error whose code field is HSX_E_DEV_MANAGED_LOGS — stable to match on in scripts and agents.
Likely causes
- The session id is stale
- The cursor or filter is invalid
- The state file is unreadable
How to fix it
- Check the session with
hs-x dev status --session <id> - Retry without a cursor to read from the beginning
Still stuck? Re-run the command with --debug for the wire-level detail, or hs-x doctor to check accounts, link state, and connectivity in one pass.
Keep going