Back to docs
Troubleshooting

Diagnose by layer before restarting everything.

Most failures are scope, route, runtime, or evidence problems. Start with the layer that changed most recently.

Common symptoms

SymptomLikely causeFirst check
403 from APIWrong actor credential or workspace scope.Check whether you need bearer JWT or x-api-key.
Agent online but not receiving workWrong workspace, project, team, role, or queue filter.List the agent and inspect its inbox in the same workspace.
Terminal opens wrong sessionStale console-router route or reused serve port.Compare agent ID, serve port, and router inventory.
Workflow stuck after PR mergedCompletion evidence not attached to handoff/run.Open workflow diagnosis and PR comments.
Provider login loopsExpired provider auth or sidecar challenge pending.Check provider sidecar status before respawning agents.
Docs page returns homepageStatic route missing from deployed bundle.Verify docker/site/docs/.../index.html is deployed.

Do not leak secrets while debugging

midfleet config redact --json
midfleet config doctor
midfleet internal status
midfleet internal inbox --name <agent> --json

When sharing evidence, summarize command results and redact tokens, API keys, provider credentials, relay secrets, and service-token values.