Troubleshooting

Symptom	Check
Model not found or no access	Confirm the model slug, hosted availability, and account access.
Session does not reach `READY`	Check SDK status/error messages, credentials, capacity, and endpoint. Do not send model commands before readiness.
State command acknowledged but no prediction	An acknowledgement is not an action reply. Set a nonblank task, inspect `command_error`, and keep both camera tracks publishing after the request.
`command_error` for `state_json`	Send a JSON string, eight finite numeric state values, and an integer `chunk_id`. Keep the serialized request within 2,000 characters.
Repeated request produces no reply	Identical JSON bytes are deduplicated. Increment the ID for a new observation; for a controlled retry, change a `retry` counter and deduplicate replies.
Actions look plausible but the task fails	Verify raw camera orientation, state coordinates, controller scaling, and gripper conversion. The service already rotates images and converts output actions.
Reply belongs to an old observation	Match request IDs, allow one request at a time, and discard timed-out results. Frame delivery is not synchronized capture.
No reply after reset	Send changed request bytes and fresh frames; resetting does not clear the task instruction or advance the robot.

The helper unwraps message data. To inspect request rejections, subscribe to command_error before connecting and consume that queue alongside predictions in your application. SDK command errors and asynchronous model rejections are separate paths. For a report, include SDK version, confirmed model slug, request ID, frame shapes, and the error reason. Describe whether the observations were synthetic, simulated, or from hardware. Do not attach API keys or private camera recordings.

Get started

Models

Troubleshooting