Why is my TradingView alert not triggering?
Check the server-side alert instance, not only the current chart. Alerts use a saved snapshot; repainting, expiration, runtime errors and frequency limits can also explain missing alerts.
Why this matters
Trading automation is a chain. A correct chart signal does not prove that webhook delivery, routing, cTrader submission and broker acceptance all succeeded. Diagnose the last stage that definitely worked, then inspect the next one.
Pine / TradingView signal
→ TradingView alert
→ Webhook delivery
→ Receiver validation/routing
→ cTrader execution
→ Broker result
→ Order/position
Real-world scenarios
Scenario A — Old snapshot
Record the symptom precisely, identify the last successful stage in the automation chain, and verify the next stage with logs or an exact error result. Correct that stage only and reproduce the test on demo before live use.
Scenario B — Intrabar signal vanished
Record the symptom precisely, identify the last successful stage in the automation chain, and verify the next stage with logs or an exact error result. Correct that stage only and reproduce the test on demo before live use.
Scenario C — Expired alert
Record the symptom precisely, identify the last successful stage in the automation chain, and verify the next stage with logs or an exact error result. Correct that stage only and reproduce the test on demo before live use.
Scenario D — Runtime error
Record the symptom precisely, identify the last successful stage in the automation chain, and verify the next stage with logs or an exact error result. Correct that stage only and reproduce the test on demo before live use.
Scenario E — 15-in-3-min limit
Record the symptom precisely, identify the last successful stage in the automation chain, and verify the next stage with logs or an exact error result. Correct that stage only and reproduce the test on demo before live use.
Diagnostic workflow
- Confirm the Pine condition in realtime.
- Confirm the intended TradingView alert is active and inspect its log.
- Record webhook delivery status and exact HTTP result.
- Confirm the receiver/NRUNO accepted or rejected the command.
- Confirm cTrader connection, target account and exact broker symbol.
- Read the cTrader/broker result and exact error code.
- Verify the final position state matches the requested action.
Worked example — EURUSD
A long signal for EURUSD fires in TradingView. The alert message identifies the action and symbol. The receiver validates it, resolves the broker symbol and dispatches it to cTrader. If cTrader returns BadVolume, UnknownSymbol, MarketClosed or another execution error, the TradingView signal and webhook may both have worked correctly. The failure belongs to the execution stage.
Worked example — broker-specific naming
TradingView may use XAUUSD while a broker exposes a different label or suffix. The alert can fire and the webhook can be accepted while execution still fails. Symbol mapping must therefore be explicit and transport success must be logged separately from broker acceptance.
Reliability rules
- Give each signal a lifecycle: received → validated → dispatched → accepted/rejected.
- Use a unique signal ID where possible and make processing idempotent.
- Never put broker passwords or other secrets in webhook messages.
- Acknowledge webhook requests quickly; do not wait for slow broker fills.
- Test malformed messages, duplicate delivery, closed markets, disconnects, symbol mismatches, entries and exits on demo.
- Show exact error states instead of a generic “failed”.
NRUNO context
NRUNO is the execution connector, not the signal generator. It should be described as receiving the user’s TradingView instruction and routing it toward cTrader. It should never be presented as choosing trades or guaranteeing fills or profitability.
For this problem class, NRUNO distinguishes: signal received; validation rejected; cTrader unavailable; command dispatched; broker/cTrader accepted; broker/cTrader rejected with reason; duplicate ignored.
Common mistakes
- Confusing Strategy Tester fills with live broker execution.
- Editing Pine code without recreating an existing TradingView alert.
- Using ambiguous BUY/SELL commands for exits.
- Ignoring broker symbol names or volume rules.
- Retrying without duplicate protection.
- Blaming TradingView for a broker-side rejection.
- First-testing new automation on live funds.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.