Troubleshooting - Reactor

Symptom	Check
Connection rejected or no capacity	Use `https://api.reactor.inc`, the correct model identifier, and an authorized key. Capacity errors can occur before inference; retry with backoff or contact Reactor.
No first chunk	Send `get_status` and read `waiting_for`. The session needs a task, 25 frames of every camera, and 25 valid rows of robot state.
No next chunk	Echo the last received `step` with `set_executed_step`. `session_status.awaiting_step` shows the value the session expects.
`prediction_failed` with `too_large`	Scale each frame down, and keep its aspect ratio. Send frames no larger than 512 × 288 (width × height).
`prediction_failed` with `invalid_input`	Check that `robot_state_json` parses, rows are finite, quaternions are nonzero.
`prediction_failed` with `task_too_long`	Shorten the task to 64 tokens or fewer. The 300-character limit alone does not guarantee this.
State ignored	Encode the state as a JSON string inside `robot_state_json`. Check the 16,000-character limit.
Correct shape, wrong motion	Check camera identities, the pose frame, quaternion order, and that you treat poses as absolute targets. Row counts do not prove embodiment compatibility.
Gripper moves the wrong way	Gripper values are absolute with `0` open. Convert your driver’s units and polarity explicitly.
Chunk has fewer rows than expected	A chunk that starts an episode has 21 rows. This follows a new session, `reset_context`, or a failed prediction.

Report a problem

Include this information in your report:

The model identifier, the SDK and client versions, and the session ID
Timestamps, track names, and frame sizes
The number of robot state rows
The last received step and the last echoed step
The session_status reply and the exact error text
When the failure occurred: during connection, at the first prediction, or at a later chunk

Do not include an API key.

⌘I