View as Markdown

timeout

No answer in time: a batch leg's status, or a pre-trade hook's `error` in webhook events. For a batch leg the order may have executed.

Not an HTTP error. Unknown: it may have executed. Resolve it with the same idempotency key before acting.

Likely causes:

  • The terminal or broker did not reply in time.
  • Your pre-trade hook did not answer in time.

What to do: Batch legs: never resend blindly; repeat the batch with the same Idempotency-Key, or check positions and history. Hooks: make the hook answer faster.

Retry: Only with the same Idempotency-Key (or clientId). The first attempt may have executed; never resend a trade blindly.

Listed under Orders and idempotency in Errors. Send the error’s requestId to support and we can find the request.