Skip to main content

Connection Recovery

An application disconnect does not mean that provider-side orders were canceled. Working orders and positions can remain active at the broker or exchange while HyperionX has no current updates.

Never blindly resubmit an unknown order

If an order submission times out or the connection drops before acceptance is known, do not submit the same intent again until the provider account proves whether the first order exists. A second submission can create duplicate exposure.

Automatic Reconnect​

After an unexpected disconnect, the current connection framework can make up to ten reconnect attempts while the connection remains enabled. The delay increases between attempts.

During a disconnect:

  • local account views can become inactive
  • provider event subscriptions stop
  • working orders can remain live at the provider
  • displayed balances, positions, orders, and PnL can be stale

Reconnect restores transport, but provider state must still be reconciled before trading resumes.

Recovery Procedure​

  1. Stop new order entry, strategies, MegaDOM actions, and Trade Copier actions.
  2. Open the broker or exchange's authoritative application or website.
  3. Record open positions, working orders, recent fills, and account balance.
  4. Allow HyperionX to reconnect or reconnect it manually after automatic attempts stop.
  5. Wait for account, position, order, and execution state to reload.
  6. Compare HyperionX with the provider account.
  7. Resolve every difference before enabling automation or placing another order.
  8. Cancel or flatten from the provider interface if HyperionX state remains uncertain.

Unknown Submission Outcomes​

An unknown outcome means HyperionX sent a command but did not receive authoritative proof of acceptance or rejection.

Use this order of authority:

  1. Provider order identifier or provider-side order record.
  2. Exact client order identifier reconciliation where supported.
  3. Provider execution and fill records.
  4. HyperionX local status only after reconciliation.

Do not infer rejection from a timeout, disconnected icon, missing chart banner, or an empty local grid.

Provider Notes​

KuCoin​

KuCoin includes client-order-identifier reconciliation and safety holds for supported routes. If reconciliation remains pending, leave the hold in place and verify the exact Spot or Futures account at KuCoin.

Rithmic​

Rithmic can replay account, order, and position state after reconnect. Verify the exact Rithmic account identity because a connection can expose multiple broker accounts. Confirm protective orders at Rithmic before replacing them.

Hyperliquid​

After reconnect, verify main-wallet account state, agent approval, builder-fee approval, open orders, and positions. A local wallet disconnect is not provider-side revocation.

Binance​

Binance is Unavailable / Coming Soon for a clean supported setup. The picker locks new setup, and legacy preconfigured state is not release-certified. Do not use legacy Binance state as a public reconnect or reconciliation workflow.

Reconnect Validation Before Release​

For each supported provider and account type, test:

  • disconnect with no working orders
  • disconnect with one working order
  • disconnect during submission
  • disconnect during cancel or change
  • reconnect after a partial fill
  • reconnect with an OCO or bracket active
  • application restart with provider-side exposure still open

Document the provider result and do not assume another provider behaves the same way.

Related pages: