Changed your strategy settings? Recreate the strategy alert to apply those changes to your automation. TradingView keeps a separate copy of the strategy when you create an alert. Editing the chart doesn’t refresh that copy. The chart can use your revised settings while the running alert keeps sending signals from the earlier version.
Table of Contents
- Key takeaways
- Why does the running alert still use your old settings?
- When should you recreate strategy alerts?
- Can editing the alert replace recreating it?
- Recreate Strategy Alert: Step-by-Step Checklist
- 1. Record the current deployment
- 2. Check open positions and working orders
- 3. Apply and review the revised chart settings
- 4. Check the PickMyTrade message and destination
- 5. Retire the old alert and create the replacement
- 6. Validate a controlled entry and exit
- Which alert condition should you select?
- What happens to open trades when you recreate the alert?
- How can you verify the replacement is using the new settings?
- Frequently asked questions
- Make alert replacement part of your strategy update
For traders using PickMyTrade for Tradovate automation, the update needs to cover the chart, the running alert, and the account’s existing trades. This guide shows which changes require a replacement, exactly what to check in the alert dialog, and how to avoid leaving an open position without its expected exit signals.
This workflow covers the standard TradingView strategy-to-Tradovate route on pickmytrade.trade. Use the strategy automation requirements to confirm that your script and generated message suit that route.
Key takeaways
- A running alert uses saved strategy settings; chart edits don’t refresh that copy.
- Recreate strategy alerts after changes to the strategy’s code, inputs, symbol, timeframe, or relevant properties.
- Plan the handover around open positions and protective orders.
- Verify the replacement through TradingView, PickMyTrade, and broker records before relying on it.
Why does the running alert still use your old settings?
The alert and your chart are separate instances. TradingView’s strategy alert documentation explains that its server-side copy operates independently. Deleting the previous alert and creating another is the documented way to apply changed strategy settings.
Consider a hypothetical moving-average strategy. You create an alert with a length of 20, then change the chart input to 50. The chart recalculates using 50. The existing alert remains tied to its earlier configuration. Comparing its later signals against the edited chart can therefore make a working alert appear incorrect.
| Illustrative setting | Edited chart | Existing alert | Replacement alert |
|---|---|---|---|
| Moving-average length | 50 | 20 | 50 |
| Configuration used | Revised inputs | Saved earlier inputs | Inputs saved at new creation |
Keep a simple version record whenever you update automation: script version, inputs, symbol, timeframe, and alert creation time. It gives you a concrete way to identify which settings produced a later signal.
When should you recreate strategy alerts?
Recreate the alert after changing the strategy configuration you want it to run. Inputs, code, timeframe, symbol, and relevant strategy properties belong in that check. Delivery-only changes, such as correcting a webhook address, need a separate review of the alert’s message and notification fields.
| Change | Recommended action |
|---|---|
| Pine Script entry, exit, or filter logic | Create a replacement from the revised script. |
| Strategy inputs, such as lookback or stop distance | Create a replacement with the intended input values. |
| Chart symbol or timeframe | Create a replacement on the intended market and interval. |
| Strategy properties affecting sizing or calculations | Recreate and verify the resulting order behavior. |
| Alert name or notification preference only | Edit the applicable alert field; this does not refresh strategy logic. |
| Webhook URL or message only | Review the delivery configuration separately; recreate if strategy settings also changed. |
TradingView’s Pine Script documentation identifies the script, inputs, symbol, and timeframe as part of the saved alert context. After an update, compare that complete set with your intended setup. A familiar chart layout or alert name can hide a changed input.
Be especially careful with size changes. A strategy quantity and an execution payload’s quantity can come from different settings. Changing one doesn’t prove the other changed. Inspect the generated message and your integration’s sizing rules before assuming a chart quantity of two will produce an account order of two.
Can editing the alert replace recreating it?
Use alert editing for the delivery fields you intend to change. Use a replacement alert to capture revised strategy settings. TradingView’s documented recreation procedure is the reliable reference for this distinction; renaming an alert or updating its webhook address doesn’t demonstrate that its strategy copy has changed.
For example, changing where a message is delivered and changing the moving-average length solve different problems. If you change both, review both. Check the saved strategy settings and the destination before the replacement is allowed to send orders.
Use TradingView’s Alerts Manager to inspect status and manage the old alert. Keep a copy of its configuration before removal, but protect account tokens and webhook credentials. An alert name is useful for tracking versions; it isn’t evidence of the underlying settings.
Recreate Strategy Alert: Step-by-Step Checklist
Start by recording your current setup and checking the actual Tradovate account. Then prepare the revised chart, replace the old alert at a planned handover point, and test the new route. Complete the steps in order so you know which alert is responsible for the next instruction.
1. Record the current deployment
Write down the current script version, inputs, symbol, timeframe, strategy properties, alert condition, and destination account. Save the existing message securely. Include whether entries, exits, or both depend on TradingView signals. This record helps you distinguish an intended change from an accidental difference in configuration.
2. Check open positions and working orders
Check Tradovate for open positions, pending entries, and protective orders. Decide how every existing position will be managed during the switch. If its exit depends on the old TradingView alert, stopping that alert removes a signal path you may still need.
Switching while the account is flat can simplify the process. Still check for working orders that could fill later. If you must change with a trade open, identify its exit owner and preserve the required protection before stopping the old alert.
Stopping or deleting a TradingView alert does not itself close a Tradovate position or cancel an order already submitted. A webhook already sent may also still be processed. Check the account again during the handover, and use explicit broker or supported order-management controls for any intended close or cancellation.
3. Apply and review the revised chart settings
Load the intended script version and set its inputs. Verify the exact symbol, exchange or feed, timeframe, and relevant strategy properties. Review the chart’s orders and Strategy Tester to understand the revision. Treat that review as a strategy check, then separately validate the external execution configuration.
4. Check the PickMyTrade message and destination
In PickMyTrade, open Generate Alert and confirm the intended Tradovate account. Review the sizing, symbol mapping, and exit configuration. Copy the generated JSON and the webhook URL shown for that setup. Follow the TradingView alert configuration guide rather than reusing an endpoint from an old tutorial.
A change to a strategy input doesn’t necessarily require different PickMyTrade JSON. A previously validated message may remain appropriate when routing and execution settings stay the same. Regenerate or revise it when those settings change. In either case, verify the message rather than copying it without review.
5. Retire the old alert and create the replacement
At the planned switch, stop the old alert and retain the settings you need before deleting it. Check that no other alert is sending the same instructions to this account. Then create the replacement from the revised strategy using the field checklist below.
- Open Create Alert from the updated strategy’s menu or select that strategy in the alert dialog. Confirm the intended chart symbol and timeframe before creation.
- Under Condition, select the intended strategy. For the standard PickMyTrade strategy integration, select Order fills only where that choice appears.
- Paste the appropriate generated JSON into Message. Check account, instrument, action, sizing, and any required placeholders.
- In Notifications, enable Webhook URL and paste the URL copied from the current PickMyTrade setup.
- Check the alert name and expiration. Create the alert when the account handover is ready, then confirm its active status in the Alerts Manager.
Give the replacement a clear name, such as MA50_15m_v2, with no account secrets. Record its creation time alongside the deployment settings. A timestamp provides a useful boundary: you can investigate whether a questionable signal came from before or after the change.
6. Validate a controlled entry and exit
Test the intended configuration in a connected Tradovate demo account before relying on it live. Wait for a valid realtime event; don’t change the production timeframe merely to force a faster signal. Match the TradingView log entry to the received alert and Tradovate order. Test the exit as well as the entry.
Which alert condition should you select?
For the standard PickMyTrade strategy route, use Order fills only when the dialog offers event choices. The setup documentation specifies this selection. Here, an order fill means a TradingView broker-emulator event; the eventual Tradovate execution must be checked separately.
TradingView’s alerts FAQ also describes scripted alert() events. Those require an intentionally designed message route. Selecting both event types can add messages you didn’t intend to trade. If your script uses a custom alert route, confirm that integration before substituting it for the standard order-fill setup.
Custom order messages also need the expected placeholder configuration. When a Pine strategy supplies an alert_message value in its order calls, TradingView documents {{strategy.order.alert_message}} for passing that value into an order-fill notification. Don’t replace a working integration message with this placeholder unless the script and integration require it.
What happens to open trades when you recreate the alert?
A replacement alert doesn’t automatically take ownership of an existing Tradovate trade. Its strategy state comes from its own calculations. Compare that state with the actual account, then decide which process will manage any existing position. A matching direction on the chart is insufficient to establish matching quantity or exit behavior.
Consider another hypothetical example: the broker holds a long position opened under the previous strategy. The revised chart shows a different simulated trade sequence. Turning on the replacement doesn’t explain which future signal should close the broker’s existing long. Resolve that question before allowing the new signals to affect the account.
Inspect the actual working stops and targets in Tradovate. A broker-held protective order has different dependencies from an exit waiting for a future webhook. Keep the required protection and remove obsolete orders only as part of an intentional plan. The trade monitoring guide explains where to review execution records.
How can you verify the replacement is using the new settings?
Verify the replacement across TradingView, PickMyTrade, and Tradovate. Active status confirms that the alert is enabled; it doesn’t prove correct sizing or a successful broker fill. Collect the evidence below for a controlled entry and exit before considering the update complete.
| Check | Evidence to collect |
|---|---|
| Strategy configuration | Script version, inputs, symbol, timeframe, and properties recorded at creation. |
| TradingView event | Replacement alert name, trigger time, and relevant log entry. |
| PickMyTrade receipt | Matching received alert and the expected account, symbol, action, and quantity. |
| Broker outcome | Accepted, rejected, or filled order details and resulting position. |
| Exit handling | Expected close behavior and protective orders verified against actual exposure. |
Investigate the first stage that fails. No TradingView event calls for checking the condition, active status, market data, and script behavior. A received alert followed by a rejection calls for reading the rejection. Use the alert error reference to investigate the reported cause.
For support, collect timestamps with timezone, the alert version, intended settings, and the relevant order ID or rejection text. Redact tokens and credentials. Keep the same records after the first successful test so the next strategy update starts from a known setup.
Frequently asked questions
Saving your edited script doesn’t refresh the existing alert’s saved copy. If you want the revised code to govern future strategy alerts, create a replacement using that version. Record the change and review the account handover before enabling it for execution.
Yes, when you want the running strategy to use that new timeframe. The existing alert retains its creation context. Verify the symbol and inputs at the same time, then confirm that the replacement’s intended signal timing matches your strategy design.
TradingView calculates strategy history before continuing in realtime, but strategy alert notifications concern realtime events. Don’t expect alert recreation to replay past entries into your account. A historical chart position also doesn’t prove that the broker holds a matching position.
Only when the required execution configuration or message content changes. A revised strategy input can leave routing unchanged. Check the existing message against the intended account, instrument, sizing, and exits. Use the broker-specific generator or documentation when those details need updating.
Check whether the previous alert remained active, whether another alert targets the same account, and whether multiple event types sent instructions. Compare TradingView logs with received messages and broker orders. Duplicate exposure needs investigation across the whole path; the chart alone won’t identify every source.
Make alert replacement part of your strategy update
Make alert replacement part of every strategy change you intend to trade. Record the new settings, settle the handling of existing positions, replace the old alert, and verify the resulting entry and exit. That sequence gives you a clear record of what changed and which account behavior was checked.
Before your next change, follow the PickMyTrade TradingView alert setup guide with the intended Tradovate account selected. Save the alert creation time alongside the revised settings, then check the next qualifying realtime event through to the broker record.
Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.
Also Checkout: Automate TradingView Indicators with Tradovate Using PickMyTrade
