Retain the original command payload, idempotency key, command ID, and trading connection. Resolve the previous outcome before issuing a replacement.
Select a numbered step to zoom straight to that control.
After a lost response
Keep the original idempotency key and exact command payload.
Check the command result through the same trading connection. If still uncertain, compare Orders, Trades, and Positions.
Do not submit a new order with a new key until the previous outcome is known.
Rebuild state
Load current state and all history pages, preserving each cursor until finished.
Continue with private events from the saved sequence and deduplicate by event ID.
If the cursor is invalid, rebuild state and reconcile resources. Very old events may predate durable event storage.
Common questions
Should I retry with a new idempotency key?
First recover the original result. A new key represents another command and can duplicate exposure if the first request already succeeded.
My saved event cursor is no longer valid.
Reload authoritative state and history pages, reconcile orders and positions, then continue from a valid event sequence. Deduplicate events by their IDs.
You’re done when…
The existing command’s outcome is resolved before any fresh order is considered.
If this does not match what you see, use Common questions above or contact support with the page and account details.Continue in QATS
Open the relevant screen to follow the steps in this guide.
Tell us where you got stuck. Never share passwords or access keys.