How should cTrader automation handle minimum stop distance?

What this means in practice

Validate the requested protective stop against the symbol/broker's current rules before submitting or modifying it. If invalid, reject or adjust only according to an explicit user-approved policy. This page is specifically about “How should cTrader automation handle minimum stop distance?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Stop too close

Validate protection in the symbol's real units: direction, price-versus-distance convention, tick size/digits and current minimum distance. Record the normalized value actually sent to cTrader. For Scenario A — Stop too close on question 87, use that evidence specifically to answer “How should cTrader automation handle minimum stop distance?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Spread effect

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 B — Spread effect on question 87, use that evidence specifically to answer “How should cTrader automation handle minimum stop distance?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Changing broker rule

Inspect the mechanism named by “Scenario C — Changing broker rule” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Changing broker rule on question 87, use that evidence specifically to answer “How should cTrader automation handle minimum stop distance?”; 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 cTrader automation handle minimum stop distance?”, 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.