TradingView alert still using your old script?

Your chart and your running alert are separate

When you create an alert, TradingView stores a server-side copy of the script, inputs, symbol and timeframe. Later chart changes do not replace that copy. This explains why an edited exit condition or a corrected message can look right on the chart while the old alert keeps sending something else.

For code or input changes, delete the old alert and create a new one from the updated chart. Editing its name is not a script refresh. TradingView's alert FAQ confirms this behavior.

A controlled replacement, without duplicate entries

Our recommended NRUNO workflow keeps the old and new alert from trading the same setup at once:

1. Check open positions first. If the existing alert supplies their exits, plan the handover before stopping it. Do not leave a live position dependent on an alert you have removed.
2. Record the old setup. Keep its name, condition, message, symbol, timeframe and relevant inputs. Store its webhook URL privately.
3. Stop the obsolete route. Once existing positions are accounted for, stop the old alert. Keep the test route on a demo account.
4. Prepare the current chart. Save the script, apply the intended version, and confirm its inputs, symbol and timeframe.
5. Create the replacement. Choose the intended script and event type, check the message and webhook destination, and give it a recognizable name. Delete the obsolete alert after recording what you need.
6. Observe one new event. Match its alert-log entry to NRUNO and the demo account. Check entry and exit separately before moving to live use.

A useful naming pattern is EURUSD-15m-FVG-v3-demo. It helps you distinguish versions in the alert list; the name alone does not change the signal's content.

Check the message, not just the script name

For an NRUNO strategy that supplies a JSON object in every relevant order's alert_message, the order-fill alert can use:

{"tvAlertTime":"{{timenow}}","payload":{{strategy.order.alert_message}}}

The inner placeholder is intentionally unquoted. It must become a valid JSON object, not an empty value or plain text. A strategy with no message on an exit can still fail on exits even if its entry worked. Check the actual emitted message in TradingView.

This is not a universal indicator message. Use the NRUNO setup examples for indicator buy, sell and exit alerts. Unsure which event to select? Compare alert(), alertcondition() and order fills.

If the replacement still appears wrong

Two instructions arrive for one setup

Compare alert names and creation times. Look for a second active alert or both order-fill and alert() events being used for the same action.

No new alert appears in TradingView

Check that it is active, its selected condition is correct, and the script has no runtime error. An old marker on the chart is not a new realtime event.

TradingView reports a delivery failure

Inspect the status and emitted body with the webhook error checklist; repeatedly recreating the same invalid message will not fix delivery.

NRUNO received it but cTrader did not trade

Open the signal's details, check the rejection reason and confirm the intended cBot/account is connected. Keep the test on demo while correcting it.

Alerts operate on realtime events, not a replay of every historical marker. See TradingView's alert concepts.

What to send if you need help

Send the alert name and creation time, symbol, timeframe, the emitted message with secrets removed, and NRUNO's signal ID if available. Tell us whether the unexpected action was an entry or an exit. This gives support one event to trace instead of guessing from a chart screenshot.