Trading bot outage: an incident plan without duplicate orders — Illustrative trading workspace, not a product or performance screenshot

AIMarkt · knowledge & practice

Trading bot outage: an incident plan without duplicate orders

During an outage, uncertainty about existing orders matters more than an immediate restart. Begin with the account where trades are actually executed.

Illustrative trading workspace, not a product or performance screenshot

Do not blindly retry

A timeout means software received no answer. The exchange may still have received the order. A repeated instruction can open another position. Check platform history and existing exposure first.

Gather facts before restarting

Record timezone, instrument, request ID, platform order ID and error message. Distinguish a delayed display from interrupted data or execution. Never share API secrets, seed phrases or passwords. Screenshots can help but do not replace order history.

Assign recovery responsibility

Record who pauses new orders and who monitors existing positions. Cancelling everything can remove protective exits. Resume only once account state is understood, then check the first new instruction separately. Priority support starts at Titan, but does not guarantee prevention of trading losses.

Checks before proceeding

  1. Check the exchange before retrying.
  2. Keep IDs and error codes.
  3. Check protective orders remain intact.

Worked example

Retrying a €100 order already filled after a timeout can increase exposure to €200.

Sources and limitations

These articles use AIMarkt package terms and general execution explanations. Examples are illustrative, not customer results. No independent performance report or proof of every platform feature is published here. Consult official platform documentation and the FCA for UK rules. Translation does not establish permission to provide services in the UK.

Continue reading