What if the webhook is accepted but cTrader execution later fails?
Treat webhook acceptance and cTrader execution as separate statuses. If cTrader later rejects the operation, log and expose the exact execution error instead of pretending webhook delivery failed.
What this means in practice
Treat webhook acceptance and cTrader execution as separate statuses. If cTrader later rejects the operation, log and expose the exact execution error instead of pretending webhook delivery failed. This page is specifically about “What if the webhook is accepted but cTrader execution later fails?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — BadVolume after acceptance
Compare requested size with the cTrader symbol minimum, maximum and step. Convert to one canonical internal unit, normalize once, and log requested versus submitted volume. For Scenario A — BadVolume after acceptance on question 36, use that evidence specifically to answer “What if the webhook is accepted but cTrader execution later fails?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Market closes before execution
Inspect the mechanism named by “Scenario B — Market closes before execution” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Market closes before execution on question 36, use that evidence specifically to answer “What if the webhook is accepted but cTrader execution later fails?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Connection drops after acceptance
Inspect the mechanism named by “Scenario C — Connection drops after acceptance” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Connection drops after acceptance on question 36, use that evidence specifically to answer “What if the webhook is accepted but cTrader execution later fails?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- TradingView alert log and exact send time
- HTTP status and receiver timestamp
- validated payload plus signal ID
- cTrader result only after transport is proven
Practical rule
For “What if the webhook is accepted but cTrader execution later fails?”, 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: Treat webhook acceptance and cTrader execution as separate statuses. If cTrader later rejects the operation, log and expose the exact execution error instead of pretending webhook delivery failed.
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.