NRUNO Trading Automation Wiki · Question 63

How long should a TradingView webhook signal remain valid before it becomes stale?

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

Give time-sensitive signals an explicit creation time and expiry policy. A delayed entry that was valid 30 seconds ago may be dangerous after a disconnect or market move, so stale commands should not automatically become fresh trades.

What this means in practice

Give time-sensitive signals an explicit creation time and expiry policy. A delayed entry that was valid 30 seconds ago may be dangerous after a disconnect or market move, so stale commands should not automatically become fresh trades. This page is specifically about “How long should a TradingView webhook signal remain valid before it becomes stale?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Five-second outage

Inspect the mechanism named by “Scenario A — Five-second outage” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Five-second outage on question 63, use that evidence specifically to answer “How long should a TradingView webhook signal remain valid before it becomes stale?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Two-minute disconnect

Inspect the mechanism named by “Scenario B — Two-minute disconnect” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario B — Two-minute disconnect on question 63, use that evidence specifically to answer “How long should a TradingView webhook signal remain valid before it becomes stale?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — Signal arrives after session closes

Inspect the mechanism named by “Scenario C — Signal arrives after session closes” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Signal arrives after session closes on question 63, use that evidence specifically to answer “How long should a TradingView webhook signal remain valid before it becomes stale?”; 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 “How long should a TradingView webhook signal remain valid before it becomes stale?”, 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: Give time-sensitive signals an explicit creation time and expiry policy. A delayed entry that was valid 30 seconds ago may be dangerous after a disconnect or market move, so stale commands should not automatically become fresh trades.

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.