summary: if your TradingView alert fired but nothing showed up in your edgeful trade log, the webhook URL isn't connecting the two properly — here's how to compare your URLs and fix the issue.

before diving into webhook troubleshooting, make sure the alert actually triggered in TradingView:

if the alert isn't in the log, the issue is earlier in the chain — see TradingView alert didn't fire instead.

if the alert is in the log but nothing shows up in your edgeful trade log, the problem is the webhook connection between TradingView and edgeful.

the most common cause is a mismatch between the webhook URL in your TradingView alert and the one in your edgeful strategy. even a single character difference means the signal never reaches edgeful.

here's how to compare them:

in TradingView, open your alerts panel and find the active alert for the algo. click to edit it and copy the full webhook URL from the webhook URL field.

in edgeful, go to the algo dashboard (algos → dashboard) and find the strategy. the webhook URL is in step 2 of the setup flow.

you can either click the copy button beside "view webhook" — or click "view webhook" to open the popup and use the copy button there.

paste both URLs side by side and confirm they match exactly. the full webhook URL should look something like this:

https://algos.edgeful.com/trading/webhook/your-strategy-id/your-secret-key (your own URL has your strategy's real ID and key in those two spots, so keep it private)

this is a common gotcha. when copying the webhook URL, make sure you're getting the full URL — not a truncated version. TradingView and some browsers can visually cut off long URLs.

a truncated webhook looks something like this:

https://algos...b279...-was

that's not usable — it's missing most of the URL. if your webhook looks like that, re-copy it using the copy button (not by selecting the text manually) and paste it into a text editor to verify the full string is there.

the webhook URL must go in the webhook URL field in TradingView's alert settings — not in the alert message body. if it's pasted into the message box instead, TradingView won't send the signal to edgeful.

open your alert, check that the webhook URL field (at the bottom of the alert configuration) has the full URL, and that the message body doesn't contain the URL by mistake.

each edgeful strategy has its own unique webhook URL. if you deleted and recreated a strategy in the automation dashboard, the new strategy has a new webhook — and your TradingView alert is still pointing to the old one.

if you've recently recreated a strategy, copy the new webhook from step 2 of the automation dashboard and update your TradingView alert.

edgeful can only process alerts once they appear in TradingView's alert log. if an alert enters the log at 9:50 AM, that's when edgeful starts processing — any delay before that point is on TradingView's side, not edgeful's.

if the trade shows up in your edgeful trade log but it arrived later than expected, check the timestamp in the TradingView alert log against the trade log timestamp. the gap between them shows where the delay occurred.

this is the one worth knowing before you assume a missing notification means something is misconfigured. TradingView makes a single delivery attempt per alert. if that attempt times out or fails, TradingView marks the alert failed in its own log and moves on — it won't resend. that's a TradingView limitation; there's nothing on edgeful's side that can force a retry.

so the two logs answer two different questions, and you need both to tell what happened:

an alert that shows as fired in TradingView with no matching entry in edgeful means the delivery itself failed — the webhook never arrived.

treat it as a no-fill. if you see a failed or timed-out webhook in the TradingView log for a trade you wanted, the trade was not placed — don't assume you're in a position. check your broker before acting either way.

these are uncommon. the vast majority of alerts deliver correctly, and when one doesn't it's usually a transient latency spike rather than anything wrong with your setup. but because a failed exit alert can leave a position open that was meant to close, it's worth periodically checking in on a running algo — see is your algo actually trading? a 60-second health check.

if the webhook URLs match exactly and you're still not seeing the trade in your edgeful trade log, reach out via the in-app chat. have these ready:

the team can compare the two on the backend and check if the signal is arriving but failing for another reason.