Troubleshooting

Symptom	Check
Repository returns 404	Use the public `reactor-team/reactor-cookbook` URL and the main-branch installation instructions in the quickstart. No GitHub organization access is required.
Session creation returns `429` with `no available capacity`	There is no available model capacity for this request. Retry later or contact Reactor; changing observation fields will not resolve it.
Session never reaches `READY`	Inspect SDK status and error logs. Confirm the API key, model access, and endpoint; the reference client allows 300 seconds for readiness.
Session is ready but no actions arrive	Set a nonempty task and keep all three correctly named tracks publishing after the request. Verify `proprio` contains 16 finite numbers and `state_json` is a JSON string.
Re-sending a request gives no reply	An unchanged `state_json` is deduplicated. Preserve the request ID and seed fields, and increment `retry`.
Replies belong to old observations	Keep only one request outstanding. Check the `step` echo, discard stale replies, and allow updated frames to clear the encoder before sending state.
Actions look plausible but move incorrectly	Check camera assignments, RGB order, `wxyz` quaternion order, coordinate transforms, gripper scale, and sequential delta integration. A valid response does not validate the robot configuration.
Reported latency is lower than application latency	The client’s timer excludes frame settling, capture, and action execution. Instrument those separately.
Simulator cannot import `X-WAM`	Copy `evaluation/X-WAM` into `third_party/RoboTwin/policy/` and launch from the X-WAM repository root.

Malformed state can be dropped without an action reply. Validate inputs locally instead of treating every timeout as a transient network error. See the wire contract for field limits and ordering. When reporting a problem, include the model identifier, client revision, SDK version, request ID, status transitions, input shapes, and timing. Keep credentials out of logs and reports.

Get started

Models

Troubleshooting