Why does cTrader return InvalidStopLossTakeProfit?

What this means in practice

InvalidStopLossTakeProfit means the requested protection parameters are invalid. Check direction, price-versus-pips interpretation, precision and broker/symbol protection rules before retrying. This page is specifically about “Why does cTrader return InvalidStopLossTakeProfit?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — SL wrong side

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 — SL wrong side on question 44, use that evidence specifically to answer “Why does cTrader return InvalidStopLossTakeProfit?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Pips interpreted as price

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 B — Pips interpreted as price on question 44, use that evidence specifically to answer “Why does cTrader return InvalidStopLossTakeProfit?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Protection 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 C — Protection too close on question 44, use that evidence specifically to answer “Why does cTrader return InvalidStopLossTakeProfit?”; keep it separate from the evidence for the other scenarios on this page.

Scenario D — Precision issue

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 D — Precision issue on question 44, use that evidence specifically to answer “Why does cTrader return InvalidStopLossTakeProfit?”; 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 “Why does cTrader return InvalidStopLossTakeProfit?”, 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.