summary: if your algo visualized a trade on the chart but TradingView didn't fire an alert, the issue is in your alert configuration — here's how to diagnose and fix it.
confirm the alert didn't fire
before troubleshooting, verify that the alert actually didn't trigger:
open TradingView and click the clock icon on the right sidebar to open the alerts panel
click the log tab — this shows every alert that has fired
look for an entry matching the time and instrument of the trade you expected
if the alert doesn't appear in the log, it never triggered. that's a TradingView-side issue — not an edgeful or webhook issue.
alert settings don't match algo settings
this is the #1 cause. review the active alert you've set for the algo and compare the settings to your current algo configuration.
any time you change your algo settings, you need to create a new alert. TradingView alerts are locked to the settings that existed when the alert was created. if you've adjusted your ORB size, TP levels, session, or any other parameter since you last set the alert — the alert is still running the old configuration.
to fix this:
delete the existing alert for that algo
confirm your indicator settings on the chart match what you want
create a new alert using the updated indicator
make sure the webhook URL is included in the new alert (copy it from the edgeful automation dashboard, step 2)
wrong alert condition
make sure your alert is set to trigger on the algo indicator's signal — not a generic price condition.
for example, if you're running an IB algo, the alert needs to reference the IB indicator's breakout condition specifically — not just "price crosses above a level." a generic condition won't carry the webhook payload that edgeful needs to execute the trade.
contract mismatch on the alert
your alert is tied to the specific contract symbol that was on the chart when you created it. if the contract has rolled since then — your alert is still on the old contract.
for live trading, always create alerts on the current front-month contract (e.g., NQM2026), not the continuous contract (NQ1!). after each quarterly rollover, delete the old alert and create a new one on the new contract.
the exception: if you're trading with ProjectX, you can use continuous contracts for live trading.
alert expired or hit its limit
TradingView alerts can expire or reach their trigger limit depending on your TradingView plan. check the alerts tab (not the log tab) to see your active alerts — if the alert is no longer listed or shows as expired, it won't fire.
recreate the alert if it's expired. if you're consistently hitting alert limits, you may need a higher TradingView plan tier.
timing discrepancy between strategy tester and alerts
TradingView's strategy tester might show a trade entry at 9:45 AM, but the actual alert fires at 9:50 AM. this is a known TradingView display difference — the strategy tester and the live alert engine process candles slightly differently.
always use the alerts log and your broker's trade log as the source of truth for timing — not the strategy tester.
getting confusing or duplicate alerts
if you're seeing multiple alerts fire for the same instrument, or alerts that don't match what you expect — the cleanest fix is to delete all alerts for that ticker and set up fresh. old or duplicate alerts can conflict with each other.
still stuck?
if the alert still isn't firing after checking the above, reach out via the in-app chat in edgeful. take a screenshot of your TradingView alerts panel (both the alerts tab showing your active alert and the log tab) — the team can compare your setup against what's expected.