How should pending orders be cancelled or replaced safely?

What this means in practice

Identify the exact pending order, confirm its state, cancel it, and only then create a replacement under a new command/version when double exposure is possible. This page is specifically about “How should pending orders be cancelled or replaced safely?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Move pending entry

Identify the exact pending order, cancel or modify it with confirmation, and give any replacement a distinct identity. Avoid a race where old and new orders remain executable. For Scenario A — Move pending entry on question 90, use that evidence specifically to answer “How should pending orders be cancelled or replaced safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Cancel invalid setup

Identify the exact pending order, cancel or modify it with confirmation, and give any replacement a distinct identity. Avoid a race where old and new orders remain executable. For Scenario B — Cancel invalid setup on question 90, use that evidence specifically to answer “How should pending orders be cancelled or replaced safely?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Replace pending

Identify the exact pending order, cancel or modify it with confirmation, and give any replacement a distinct identity. Avoid a race where old and new orders remain executable. For Scenario C — Replace pending on question 90, use that evidence specifically to answer “How should pending orders be cancelled or replaced safely?”; 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 “How should pending orders be cancelled or replaced safely?”, 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.