What happens when an EXIT signal arrives before the ENTRY is confirmed?
Correlate ENTRY and EXIT by identity and reconcile actual cTrader state. An EXIT arriving first must not blindly become an opposite entry.
What this means in practice
Correlate ENTRY and EXIT by identity and reconcile actual cTrader state. An EXIT arriving first must not blindly become an opposite entry. This page is specifically about “What happens when an EXIT signal arrives before the ENTRY is confirmed?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Network reorder
Correlate related commands with identity plus sequence/time and current cTrader state. A late command that no longer matches the position should be rejected or reconciled, not reinterpreted as a fresh opposite trade. For Scenario A — Network reorder on question 91, use that evidence specifically to answer “What happens when an EXIT signal arrives before the ENTRY is confirmed?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Entry rejected
Correlate related commands with identity plus sequence/time and current cTrader state. A late command that no longer matches the position should be rejected or reconciled, not reinterpreted as a fresh opposite trade. For Scenario B — Entry rejected on question 91, use that evidence specifically to answer “What happens when an EXIT signal arrives before the ENTRY is confirmed?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Fast reversal
Correlate related commands with identity plus sequence/time and current cTrader state. A late command that no longer matches the position should be rejected or reconciled, not reinterpreted as a fresh opposite trade. For Scenario C — Fast reversal on question 91, use that evidence specifically to answer “What happens when an EXIT signal arrives before the ENTRY is confirmed?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- intended signal/action
- last stage that definitely succeeded
- first stage that differs from intent
- final cTrader state after the event
Practical rule
For “What happens when an EXIT signal arrives before the ENTRY is confirmed?”, 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: Correlate ENTRY and EXIT by identity and reconcile actual cTrader state. An EXIT arriving first must not blindly become an opposite entry.
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.