Skip to main content

applying algo settings changes — what to do after you optimize and make algo setting changes

the full post-settings-change workflow — validate the new settings, apply them to your TradingView indicator, recreate the alert, SIM-test the webhook, and go live. covers optimizer-driven changes and manual tweaks.

Written by Brad

summary: you've changed your algo settings — now apply them. the 5-step process for taking new settings from the optimizer (or any manual tweak) and getting them into a live, tested algo.

this article covers: the full post-settings-change workflow — validating new settings, applying them to your TradingView indicator, deleting and recreating the alert, SIM-testing the webhook, and rolling it live with size. covers both optimizer-driven changes and manual tweaks. new to algo automation? start at the algo automation quickstart.

the algo optimizer makes it easy to test thousands of setting combinations and surface the top performers. but finding the winning settings is only half the job — getting them into your live algo correctly is the other half.

most issues members hit after an optimization aren't with the new settings themselves. they're with the steps that come after — missing the alert recreation, skipping the SIM test, or scaling up before the chain is proven. this article walks you through the full handoff so the algo that's live matches the algo that won the backtest.

when this article applies

any time you change a setting on your edgeful algo indicator — session, ORB size, max loss, profit target, contracts per trade, anything. the most common trigger is loading new settings from the algo optimizer, but the process is the same whether the changes came from the optimizer, the algo analyzer, or you just tweaked the inputs by hand.

if you only updated the script (purple icon on the indicator) and didn't change settings, see managing TradingView alerts after a script update — slightly different process.

the 5-step process

5 steps, in order. skipping one is the most common reason a freshly optimized algo doesn't behave the way it did in backtest.

1. validate the winning settings before you deploy them

before you push new settings live, confirm they actually held up. for an optimizer run, that means a few specific checks on the result you're about to apply.

open the report tab on the winning combination and look for:

  • the strategy health card shows low overfit risk — all 7 checks passing is the bar

  • the OOS Δ columns are tight — small win-rate and profit-factor drops between training and out-of-sample data

  • the in-sample period had enough trades — 30+ is a reasonable minimum

  • the max drawdown and consecutive losses are sizes you're comfortable holding through

if any of those are flagged, walk back and either tighten the constraints or pick a different combination from the top 20. a setup that fails the strategy health card on backtest is going to fail in live trading too — there's no version of "I'll just trade it small" that fixes overfitting.

if the OOS Δ columns or training % concepts aren't clicking yet, read understanding holdout, in-sample, and out-of-sample — the plain-english primer on what these mean.

for manual tweaks (not from the optimizer), run a fresh TradingView backtest with the new settings and upload the XLSX to the algo analyzer. check the strategic health score there. same principle — validate first, deploy second.

2. apply the settings to your TradingView indicator

two paths, depending on where the changes came from.

from the optimizer (most common)

when you've found a winning combination in the optimizer, here's the click-by-click flow:

  1. click into the winning combination row in the results table to expand the detail view at the bottom

  2. switch to the algo settings tab in the detail panel — this shows the exact configuration that won, broken down by category (backtest period, chart timeframe, session, general settings, and per-weekday rules)

  3. click the how to run this in TradingView button at the top of the algo settings tab — this opens the step-by-step copy guide

  4. open your edgeful algo indicator on the TradingView chart, click the indicator's settings icon, and copy each value from the optimizer's algo settings tab into the matching input field on the indicator

what to match exactly:

  • ticker symbol — make sure the TradingView chart is on the same specific contract the optimizer used. continuous symbols and front-month symbols can behave differently. if the optimizer used !ES, use !ES on the chart — not ES alone or ESM2026

  • chart timeframe — match whatever the optimizer's results table shows in the chart TF column (1m, 5m, or 15m). if the winner was on 5m, set the chart to 5m

  • session times — copy the start and end times from the optimizer's session field directly into the indicator

  • per-weekday settings — the optimizer shows one row per weekday in the algo settings tab. each weekday gets its own settings on the indicator — Monday's max loss, Tuesday's profit target, etc. apply each row individually. this is the most common place to miss a setting

  • direction filter (long only / short only / both) — match what won

  • strategy filters (min/max ORB size, entry cutoff, etc.) — copy all enabled filters and their thresholds

alternatively, the run this algo button on the detail panel deploys the combination as a live algo directly, skipping the manual indicator copy. use that path when you want the fastest hand-off without copying field-by-field.

from a manual tweak

open your edgeful algo indicator on the TradingView chart, click the settings icon, and update the inputs directly.

double-check you're working on the right chart. it's an easy mistake to update settings on a chart that's pointing at the wrong ticker or contract symbol — the alert will fire, but on the wrong instrument.

3. delete and recreate your TradingView alert

this is the step most members miss — and it's the one that breaks the chain silently. your TradingView alert is locked to the indicator settings at the moment it was created. changing the indicator doesn't update the alert. you have to delete it and create a new one.

your webhook URL doesn't change — it's tied to your strategy in edgeful, not your indicator settings. paste the same one into the new alert. same with the JSON message field.

the steps:

  1. open the alerts panel in TradingView (the clock icon in the right sidebar)

  2. find the alert for your edgeful algo indicator

  3. delete it

  4. create a new alert on the updated indicator — same webhook URL, same JSON message, same chart timeframe

if you skip this step, the algo will keep firing on the old settings indefinitely. no error message, no warning — it just won't reflect your new configuration. for the full alert setup walkthrough, see setting up TradingView alerts for algo automation.

4. SIM-test the new webhook

before you trust the new settings with real money, prove the chain works end-to-end. point your strategy at a SIM/demo account, wait for the next real signal to fire, and confirm the notification log shows status filled.

what you're checking:

  • the alert fires when expected (and matches your new chart timeframe)

  • the webhook reaches edgeful (status isn't pending or failed)

  • the order routes to your broker correctly — entry price matches, position size is what you set

  • the take profit and stop loss exits work — let one full trade play through, don't bail after the entry fills

if anything looks off, fix it now. it's significantly easier to debug on SIM than live. for the full SIM pre-flight walkthrough, see test your webhook before going live.

5. go live — and scale up carefully

once SIM confirms the new settings are working, move to live with 1 contract first — even if the optimizer told you the winning size was 3.

the order:

  1. create a new strategy in the algo dashboard pointed at your live broker account. don't reuse the SIM webhook — it'll keep routing to SIM

  2. copy the new webhook URL into a new TradingView alert (same process as step 3)

  3. trade 1 contract for a handful of fills. confirm slippage and execution match what you saw in backtest

  4. once you're confident the chain is clean, scale up by adjusting the contracts per trade input on the indicator

scaling up too fast is the single biggest unforced error after a settings change. the backtest doesn't know about your broker's slippage, your fill quality, or how you'll handle the first live drawdown. give yourself a small live sample before you ramp.

common mistakes

the 5 mistakes that come up over and over:

  • skipping the alert recreation — the algo keeps running on the old settings, you don't know why nothing changed

  • missing per-weekday rows — applying the optimizer's Monday settings to the indicator but forgetting Tuesday, Wednesday, etc. the indicator runs each weekday on whatever's configured — uncopied rows fall back to defaults

  • changing settings on the wrong chart — different ticker or different contract symbol, alert fires but doesn't match what you intended

  • trusting optimizer results that flagged overfit risk — the strategy health card said no, you traded it anyway, drawdown breached on week 1

  • jumping straight from SIM to full size live — first live fills are when slippage surprises happen, and a single bad ramp can wipe out the expected edge

  • reusing the SIM webhook URL on a live strategy — the orders keep routing to SIM and you wonder why your live account isn't filling

all of these are recoverable, but they're easier to avoid than to debug.

quick recap

→ validate first — strategy health card, OOS Δs, trade count
→ apply settings to the indicator (right chart, right ticker, all per-weekday rows)
→ delete and recreate the alert (same webhook URL, same JSON)
→ SIM-test for at least one full trade — entry, TP, and SL all proven
→ go live with 1 contract, then scale

related articles

start here:

find and validate your settings:

alert setup and management:

verify and go live:

Did this answer your question?