TradingView Alerts Use Old Settings: How to Update Them

You change an indicator input from 20 to 50. The chart responds immediately. An hour later, an automated trade arrives that belongs to the old setup. Before blaming the broker, check which version of the script your alert is actually running.

Changing a Pine script, its inputs, or the chart symbol or timeframe does not update an existing TradingView script alert. TradingView saves a separate copy when you create the alert. To apply those changes, delete the old alert and create a new one from the intended setup. TradingView documents this in its explanation of alert snapshots.

That rule explains the stale signal. Replacing a live automation alert takes another step: checking what the account is already holding before the new instructions arrive.

What changed, and where?

A chart is a workspace, not a remote control for every alert you have created from it. Use this distinction before editing anything else:

TradingView provides controls to edit, stop, resume and delete alerts in the Alerts Manager. Do not treat the existence of an Edit button as proof that a chart input change has reached the running script copy. This guide concerns Pine indicator and strategy alerts; a simple price alert has no Pine script snapshot to replace.

Check the outgoing message, not just the chart

For AlgoWay, the practical question is what instruction reaches the selected route. Suppose your chart now uses a different sizing input, but the alert message still contains a fixed quantity. A new chart display alone proves nothing about the quantity being sent. Inspect the actual alert message and the matching AlgoWay Webhook Logs entry.

Keep the message method consistent when rebuilding the alert:

• Strategy order messages: when your script supplies AlgoWay JSON through alert_message, select order-fill events and put {{strategy.order.alert_message}} in the alert's Message field.
• Explicit script calls: when the script sends JSON through alert(), select the corresponding alert() events. The message comes from the script call.

Those are different event sources. Enabling both can send more instructions than intended. The AlgoWay Pine Script alert examples explain the two setups; use the one your script was written for. Verify the delivered symbol, action and quantity against the AlgoWay JSON reference and your destination's rules.

Replace the alert with an account-state check

Use a demo or test destination for the replacement procedure where available. For an existing live setup, first decide how its open positions and pending orders will be managed during the change.

1. Record the working configuration. Save the script revision, input values, symbol, timeframe, event type and message method. Record which AlgoWay route it uses. Keep private webhook URLs out of shared screenshots and notes.
2. Inspect the destination account. Note open positions, pending orders and active protective orders. If exits depend on future alerts, arrange how those exits will be handled while the old alert is stopped. Stopping an alert is not a request to close a position.
3. Stop the obsolete alert before activating its replacement. Check the Alerts Manager for other copies serving the same automation. Preserve the diagnostic details you need, then delete the obsolete alert as TradingView instructs.
4. Prepare the intended chart and create a fresh alert. Confirm the script version and inputs, chart symbol and timeframe, selected event source, message, webhook notification and destination URL. Give it a recognizable name, such as MA50-15m-revision2, so you can identify the replacement in the alert list.
5. Verify a fresh event from end to end. Match its TradingView log entry to the request in AlgoWay Webhook Logs, then inspect the destination's order history and resulting position. Verify the intended exit path as well as the entry.

The alert name is a label for your records. Do not assume it is included in the webhook body or prevents duplicate orders. Two active copies aimed at the same route are still two possible sources of instructions.

The new alert does not replay the old trades

TradingView's strategy-alert documentation explains that the server copy calculates historical bars before proceeding in realtime, and does not send notifications for historical orders. Recreating an alert therefore does not deliver a backlog of entries that happened before it was created.

Consider a replacement strategy whose historical calculation leaves it long. Your broker account might be flat because that historical entry was never sent to it. A later strategy exit can then arrive without the matching live entry. This is a consequence to check, not a promise that every strategy will behave that way: it depends on the script's state and subsequent events.

Do not place a live trade merely to make the account resemble the chart. Decide explicitly whether to wait for a suitable fresh entry, manage an existing position separately, or revise the automation's startup procedure. The destination account is the evidence of what you actually hold.

What counts as a successful update?

Keep one short test record: the replacement alert's name and settings, a fresh trigger time, the message received by AlgoWay, and the destination's response. A manual route test checks the route; it does not establish which script version the TradingView alert is running. A chart marker alone does not establish either delivery or execution.

If the alert instead shows a frequency-limit stop, use the separate guide to TradingView alerts triggered too often. For an alert that remains active but behaves like yesterday's setup, start with the saved configuration. The chart may have moved on while the alert is still faithfully doing its old job.