Frozen orders that won't cancel or close in NinjaTrader

This article explains what frozen (golden) orders are, why they occur, and how to resolve them when they happen in NinjaTrader with Replikanto.

What are frozen orders?

Frozen orders (sometimes called "golden orders") are orders or positions that become unresponsive and cannot be canceled, modified, or closed through NinjaTrader's normal interface. You may click Close, Flatten, or Cancel repeatedly, but nothing happens.

Common symptoms:

• Orders show as pending but won't cancel when clicked
• Positions cannot be flattened or closed
• Order modifications don't take effect
• The issue typically affects Tradovate accounts due to API rate limits

Initial troubleshooting steps

Frozen orders are usually caused by network connectivity problems between NinjaTrader and the broker, where the connection to the order entry server is severed or unstable. Try these steps in order:

1. Disconnect and reconnect the broker connection in NinjaTrader — this refreshes the pending orders and allows them to be canceled in most cases
2. Repair the NinjaTrader database: Go to Tools > Options > Data tab, click Repair DB, then restart NinjaTrader — this can clear corrupted order state data
3. Use the broker's platform directly: If the steps above don't work, log into the broker's website (Tradovate or your broker's platform) and cancel or close orders and positions from there

Tradovate API rate limits

For Tradovate accounts specifically, frozen orders can occur when hitting the Tradovate API rate limit of 5,000 requests per hour (80 per minute) for the Tradovate/NinjaTrader connection. Once this limit is reached, orders and positions may freeze.

To avoid hitting the rate limit:

• Avoid using trailing stops on Tradovate accounts
• Don't make multiple price changes in a short period
• Minimize order modifications during active trading

NinjaTrader addressed this issue (tracked as ID NT-14091) in version 8.1.4+, which now provides a notification when the limit is reached. However, the underlying problem persists — pending orders and positions that become stuck when the limit is hit must still be managed through the Tradovate website or NinjaTrader web interface.

Platform freeze vs. frozen orders

It's important to distinguish between two situations that look similar on screen:

Frozen orders: Orders genuinely won't cancel or close, as described above. Something is stuck on the broker or communication side.

Platform freeze: NinjaTrader's interface itself stops responding for a period — the chart stops redrawing, clicks aren't registered, but the orders and executions actually completed normally in the background. A reliable sign of a true platform freeze is that NinjaTrader's own log and trace files stop being written during the hang and resume only when the interface recovers. In this case, nothing was stuck on the broker side — the trades filled, and the platform simply caught up when it unfroze.

Handling a platform freeze

When the interface locks up:

• Avoid clicking Close or Flatten repeatedly — each click queues another full round of cancel and flatten requests across every copied account at once, which can make the hang last longer (especially with Tradovate followers)
• A single Flatten All is enough — wait a few seconds before clicking again
• Or disconnect and reconnect the brokerage connection to recover

Reducing platform freezes

Keep in mind that Replikanto does not run on your chart, so it's not what draws or freezes it. The chart load comes from NinjaTrader rendering bars and running whatever indicators are applied. A single heavy or inefficient indicator can stall the whole interface.

To minimize freezes:

• Keep charts as lean as possible — only the indicators you actually use
• Avoid loading excess bars on charts
• Ensure your VPS has enough CPU cores and memory for the number of accounts you copy to

Alternative approach: Market Only mode

You may find it helpful to use the Market Only Replikanto feature, which allows you to copy only executions to follower accounts instead of sending order modifications that can count toward API rate limits. For more information, watch this explanatory video: https://youtu.be/WZ5rmeAuxZE