How should automated trading handle spread limits?
A spread filter should compare the current executable spread with a configured maximum before entry and define what happens when the limit is exceeded. Rejecting an entry is usually safer than silently delaying it until the market context has changed.
What this means in practice
A spread filter should compare the current executable spread with a configured maximum before entry and define what happens when the limit is exceeded. Rejecting an entry is usually safer than silently delaying it until the market context has changed. This page is specifically about “How should automated trading handle spread limits?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Normal spread
Measure executable bid/ask spread at the entry decision. If the configured limit is exceeded, record a deliberate rejection; waiting until spread normalizes creates a different trade. For Scenario A — Normal spread on question 74, use that evidence specifically to answer “How should automated trading handle spread limits?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — News spike
Inspect the mechanism named by “Scenario B — News spike” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — News spike on question 74, use that evidence specifically to answer “How should automated trading handle spread limits?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Spread normalizes after signal
Measure executable bid/ask spread at the entry decision. If the configured limit is exceeded, record a deliberate rejection; waiting until spread normalizes creates a different trade. For Scenario C — Spread normalizes after signal on question 74, use that evidence specifically to answer “How should automated trading handle spread limits?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- symbol metadata and unit conversion
- configured risk or management rule
- broker min/max/step or distance constraint
- normalized value actually sent to cTrader
Practical rule
For “How should automated trading handle spread limits?”, 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: A spread filter should compare the current executable spread with a configured maximum before entry and define what happens when the limit is exceeded. Rejecting an entry is usually safer than silently delaying it until the market context has changed.
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.