How to Track an Order Through Its Lifecycle

​

Start with a lifecycle record, not only an order ID

1. Submit the order request and store the request metadata you will need later: trader, strategy, symbol, nonce, client timestamp, and local submission time.
2. Bootstrap current order and strategy state from REST before you rely on realtime user-data feeds.
3. Subscribe to ORDER_UPDATE and STRATEGY_UPDATE with traderAddress and optional strategyIdHash, symbol, or reason filters.
4. Correlate updates by the stable order identity fields in the payload, plus orderMatchOrdinal and per-outcome ordinals where applicable.
5. Apply updates using the documented ordering fields, not local arrival time alone.
6. Keep the order open until a terminal state is explicit in the update stream or reconciled from REST history.

​

Use a state model that matches the platform

​

Reconnect and replay safely

1. If the WebSocket disconnects, reconnect first.
2. Resubscribe to the affected feeds.
3. Resume one update family with its own globalOrdinal history rules if you need gap repair.
4. Reconcile the target order plus its strategy state from REST before concluding the live state is complete again.

​

Important edge cases

​

Next routes

• How to Handle Order Sequencing vs Execution
• Realtime Connection Model
• Order and Account Event Reference
• Error Reference
• Glossary