Connector latency vs broker execution latency: what is the difference?
Connector latency covers receiving, validating and forwarding the signal; broker execution latency occurs after the trading request reaches the execution side. Measure them separately.
What this means in practice
Connector latency covers receiving, validating and forwarding the signal; broker execution latency occurs after the trading request reaches the execution side. Measure them separately. This page is specifically about “Connector latency vs broker execution latency: what is the difference?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Fast connector, slow broker
Inspect the mechanism named by “Scenario A — Fast connector, slow broker” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Fast connector, slow broker on question 38, use that evidence specifically to answer “Connector latency vs broker execution latency: what is the difference?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Slow TradingView trigger
Inspect the mechanism named by “Scenario B — Slow TradingView trigger” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Slow TradingView trigger on question 38, use that evidence specifically to answer “Connector latency vs broker execution latency: what is the difference?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Reconnect delay
Reconnect is a reconciliation event. Re-read actual cTrader positions and pending orders first, then decide whether queued commands remain valid. Expire stale entries and make recovery idempotent. For Scenario C — Reconnect delay on question 38, use that evidence specifically to answer “Connector latency vs broker execution latency: what is the difference?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- target connector/account identity
- exact broker symbol
- normalized order parameters
- cTrader response and final position/order state
Practical rule
For “Connector latency vs broker execution latency: what is the difference?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: Connector latency covers receiving, validating and forwarding the signal; broker execution latency occurs after the trading request reaches the execution side. Measure them separately.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.