Skip to content

Troubleshooting

Health returns 401

Cause: the client token does not match the token in the settings file.

Fix: read the token inside the client. Do not print it. If you rotated it, update the client. Keep the file mode 0600.

A run returns 503

Cause: provider setup is incomplete, or the provider rejected the call.

Fix: run sushi-agno configure again in an unrecorded terminal, confirm that the model id and base URL are ones your account can call, and restart sushi-agno. The provider must support tool calling and non-streaming chat completions. Do not paste the populated error into a support ticket.

The demo does not print SUSHI_CUSTOMER_DEMO_PASSED

Cause: the calculation check, the row count, or the session read did not match. A provider timeout still counts as a failed run. The guide says network and provider failures can still incur charges.

Fix: keep the failed task directory. Read sudo journalctl -u sushi-agno and fix the reported cause. Start the next attempt in a new task directory. Do not delete /var/lib/agno to clear one failure.

Readback after restart refuses to run

Cause: sushi-agno session writes its restart readback once.

Fix: use the directory from the run you are checking. Do not point it at a directory whose restart readback already exists if you expected a new file. The check is for an idle restart, not for a crash during a tool call.

Last updated November 11, 2026 · Suggest an improvement