NRUNO Trading Automation Wiki · Question 67

What happens to TradingView signals received while cTrader is disconnected?

Webhooks, Delivery & ReliabilityLast reviewed: 25 Aug 2026
Short answer

The system needs an explicit policy: reject immediately, queue with a short expiry, or hold for manual review. Blindly replaying every signal after reconnection can open trades that are no longer valid.

What this means in practice

The system needs an explicit policy: reject immediately, queue with a short expiry, or hold for manual review. Blindly replaying every signal after reconnection can open trades that are no longer valid. This page is specifically about “What happens to TradingView signals received while cTrader is disconnected?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Reject while offline

Reconnect is a reconciliation event. Re-read actual cTrader positions and pending orders first, then decide whether queued commands remain valid. Expire stale entries and make recovery idempotent. For Scenario A — Reject while offline on question 67, use that evidence specifically to answer “What happens to TradingView signals received while cTrader is disconnected?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Short-lived queue

Inspect the mechanism named by “Scenario B — Short-lived queue” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Short-lived queue on question 67, use that evidence specifically to answer “What happens to TradingView signals received while cTrader is disconnected?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Reconnect after signal expiry

Reconnect is a reconciliation event. Re-read actual cTrader positions and pending orders first, then decide whether queued commands remain valid. Expire stale entries and make recovery idempotent. For Scenario C — Reconnect after signal expiry on question 67, use that evidence specifically to answer “What happens to TradingView signals received while cTrader is disconnected?”; 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 “What happens to TradingView signals received while cTrader is disconnected?”, 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: The system needs an explicit policy: reject immediately, queue with a short expiry, or hold for manual review. Blindly replaying every signal after reconnection can open trades that are no longer valid.

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.