What survives a disconnect
- Native SL / TP stay attached at the exchange. A LucraX outage can't cancel them.
- Position state is reconciled when connection is restored. Closed positions are detected via REST + WebSocket catch-up.
What's at risk
- Trailing stops on venues without native trail support - LucraX emulates trailing client-side. During a disconnect the trail stops moving; the stop sits at its last position.
- Custom exit conditions that need indicator data - those conditions can't fire if candle data is missing.
- New entries are blocked while disconnected.
How LucraX recovers
- WebSocket reconnect with exponential backoff.
- REST snapshot of open positions and recent fills.
- Reconcile against internal state; close any positions that closed at the exchange during the gap.
- Resume normal signal evaluation.
What you should do
- Most disconnects resolve in seconds. No action needed.
- If a disconnect lasts more than a few minutes, check status and consider manually flattening at the exchange if the position has unprotected risk.