Connection checks
An order request timed out: how do you recover the original result?
Keep the original operation, reconcile account evidence and avoid a duplicate submission while the result remains uncertain.
Keep the original operation, reconcile account evidence and avoid a duplicate submission while the result remains uncertain.
A timeout means your software did not receive a usable answer. It does not tell you whether the venue received, rejected or filled the request. Treat that operation as unresolved. A second click with a new identifier can create a second economic action while the first is still being investigated.
Keep identification separate from duplicate prevention
A client identifier helps connect records. Idempotency is a stronger contract about what repeated requests may do. Kraken documents uniqueness of its client order identifier across open orders for a client; that is not a promise of permanent duplicate prevention after an order closes. MetaApi documents a tracking clientId on related objects. The tracking contract alone does not establish exactly-once trade execution.
Build one recovery record
- Retain the original operation ID and request version. Keep the exact account, environment, instrument, requested amount and first attempt time in the protected account workspace.
- Keep the original response or transport error and any authoritative order, deal or position IDs already received. Do not replace an unknown response with a guessed success or failure.
- Use the approved read-only recovery path for that account to inspect pending orders, positions and relevant closed-order or deal history. An immediately filled order may no longer be in the open-order list.
- Compare the original identity and request with the returned evidence. Missing history, a partial page, multiple candidates or a changed account leaves the result unresolved.
- Record the reconciliation result and its observation time. Any future action needs its own current authority and explicit decision; a recovery read is not consent to send, cancel or close.
What belongs in a support report?
Give authorized support the original reference, approximate time with timezone, the affected feature and the uncertainty shown by the interface. Keep account records in the authenticated support channel. Never attach a broker password, access token or API secret. A screenshot of a green connection badge cannot establish which order was accepted; the original receipt and matching account evidence matter.
Source check · 5 October 2026
Identifier semantics: https://docs.kraken.com/api/blog/cl-ord-id/ and https://metaapi.cloud/docs/client/clientIdUsage/ . History interfaces: https://docs.kraken.com/api-reference/account-data/get-open-orders and https://docs.kraken.com/api-reference/account-data/get-closed-orders . The recovery checklist is TradeTwin's conservative software workflow, not a vendor guarantee.
Questions worth asking
Can I treat an empty open-order list as proof that nothing happened?
No. A request may have filled, closed, been rejected or remain unconfirmed. Reconcile the original with the relevant account history and native identifiers; missing evidence remains unknown.
Does keeping the same ID make every API safe to retry?
No. Identifier and repeat-request rules differ by endpoint. Preserve the original and use the approved recovery read. This guide does not authorize a retry.
Primary documentation for further reading
API documentation describes the provider's interface. It does not certify your account or TradeTwin connector as ready to trade.