Skip to content

Troubleshooting

HTTP 401

Cause: the client does not have this instance's token.

Fix: run sushi-langgraph as ubuntu so it reads the access file. If you rotated the token, update every client. Keep mode 0600.

HTTP 409

Cause: the saved workflow conflicts with the request. A repeated id with different input is rejected. A rejected workflow cannot be restarted under the same id.

Fix: read the checkpoint with sushi-langgraph read. Start a new id when the input changed or the run was rejected.

HTTP 503

Cause: the provider is missing, unreachable, or returned a proposal that is not the two-field JSON object the workflow requires.

Fix: check base_url, model, and api_key, and confirm the model supports JSON-object mode. Then sushi-langgraph retry RUN_ID. Earlier successful nodes stay checkpointed. The proposal retry does not rerun the calculator. Do not delete the databases to clear a provider error.

The final read does not print SUSHI_CUSTOMER_DEMO_PASSED

Cause: the CSV, the calculator receipt, the report, or the checkpoint did not match, or a restart boundary was skipped.

Fix: follow the start, restart, resume, restart, read order in Getting started. Use the same result directory at each step. These checks are graceful restarts, not a power-loss test.

Last updated November 11, 2026 · Suggest an improvement