Market data delivery
Market data is the stream of prices and other information delivered through your subscribed service. The exchange, provider, connection, subscription, and application processing all play a role in what reaches your screen.
First verify whether the subscription is real-time or delayed and covers the intended instrument. Two displays can use different feeds, timestamps, aggregation, or refresh behaviour, so a visual comparison alone does not measure latency accurately.
Chart responsiveness
Chart responsiveness describes how the interface reacts: loading history, redrawing, changing instruments, and handling interaction. Historical lookback, chart types, indicators, and local resource use can affect the workload.
If interaction improves in a simpler workspace, investigate the difference systematically. That observation does not establish anything about the path a live order takes.
Order execution
An order travels through the supported connection and routing services to a venue. Acknowledgement, acceptance, and a fill are distinct events. A fill also depends on order type, price, liquidity, and queue conditions.
Confirm where protective orders and bracket logic reside for your specific integration. Do not assume every stop or order relationship continues to function in the same way after disconnection.
Match the observation to the next check
| What you notice | A useful first check |
|---|---|
| Prices appear delayed | Subscription status, instrument, connection, and provider notices. |
| Chart interaction feels slow | A simple workspace and local resource usage. |
| Order status is uncertain | Official broker order-management support and account state. |
Record timestamps with time zones and preserve relevant logs for official support. Never publish credentials, full account identifiers, or other sensitive data in a public troubleshooting post.
What a simulation can tell you
Simulation helps you practise controls and observe local workflow. Its fills and timing are not a live execution benchmark. Use it for interface testing while keeping conclusions about real market execution separate.
For definitions and platform-specific behaviour, consult the CME Group education resources and the NinjaTrader 8 help guide.