Documentation · Troubleshooting
Documentation · v0.22.0

Troubleshooting

Understand the state before retrying.

Model disconnected

Use direct reports and owner forms. Check the three model environment variables in the terminal that starts the server. Do not disclose the key.

Configured but unverified

Configuration exists, but this running server has not verified it. An explicit connection check is available in connection details. Restart intentionally clears verification.

HTTP 429, cooldown or timeout

Wait for the displayed cooldown before explicitly retrying. A verified connection does not promise capacity. There is no silent model switch or background retry. A late/incomplete task is not a successful result and cannot save candidate DRAFTs.

Qualification missing

Run the potentially billed synthetic check explicitly, or use a direct report. Never relabel an old check as passing for changed model/code.

Review expired or data changed

Open a fresh task and review the current snapshot. Do not try to reuse changed hidden parameters or an old approval token.

Unexpected forecast

Inspect dates, currencies, restricted funds, unknown account routing and expected collections. Missing evidence is not a zero balance. See Resolve facts.

For an independent walkthrough, use the task session. An agent-driven browser check does not count as a human participant.