Skip to main content

Ghost Orders

Issue​

The Execution Server shows an inactive order as active.

There may be several reasons why this happens, including:

  • A buggy execution algorithm
  • A buggy exchange API (for example, a HTTP 503 error for a REST API)

Troubleshooting Option​

To troubleshoot this issue, investigate the event history. See if you can spot the event that should have completed or cancelled the order.

If you see an event like this, report it to Deltix: support@deltixlab.com.

Please include the following information in your report:

  • Order ID
  • Order history information
  • (Recommended) Order Debugger printout.

If you do not see a terminal event in the order history, it means it somehow didn't come to Ember or was never issued. In this case, take a look at the trading connector logs.

Workaround Option​

Try cancelling the order using the Cancel command.

If Cancel doesn't work, use the Discard Order command in the Execution Server (ES) Monitor.

caution

Use the Discard Order command with caution. It simply marks an order as cancelled. It does NOT make any attempts to communicate the cancellation to order the execution venue. This is what the Cancel command is for.