Why Your TradingView Alert Fired But Your Trade Didn't Execute

You watch your TradingView chart. The alert fires. You flip to your broker. Nothing.

This is the most common frustration in trading automation. It happens to experienced traders and beginners alike, and it almost always has a fixable cause.

The execution chain you need to understand

When TradingView fires an alert, it does not go directly to your broker. It travels a chain:

1. TradingView fires the alert
2. TradingView sends a webhook to RelayDesk
3. RelayDesk processes the signal and routes the order
4. Your broker receives and executes it

Each link in that chain can fail. Knowing which one broke is how you fix it.

Step 1: Check your alert configuration

The most common culprit is the alert itself. Open TradingView and confirm:

• The alert is still active (alerts expire or hit their trigger limit)
• The webhook URL in the alert is the correct RelayDesk URL, with no typos or missing characters
• The message body matches exactly what your RelayDesk signal expects
• The alert frequency is set to "Once Per Bar Close," not "Once Per Bar"

That last point matters more than most traders realize. If your alert fires mid-bar and your strategy repaints on close, you get triggers that should not exist. "Once Per Bar Close" waits for the candle to complete before firing.

Step 2: Check Signal History in RelayDesk

Open RelayDesk and navigate to Signal History. This log shows every webhook that reached the platform: whether it was received, what it contained, and what action it triggered.

• If your alert does not appear in Signal History at all, the problem is between TradingView and RelayDesk. Start by confirming the webhook URL and checking whether the TradingView alert is still active.
• If the alert does appear in Signal History but no trade was placed, look at the status and error message.

Common reasons include:

• The signal message did not match the expected format
• Your bot was paused, archived, or had already hit its daily loss limit
• A position was already open and your bot does not allow concurrent entries

Step 3: Check your bot's status and settings

A bot that is paused, over its daily trade limit, or running in paper trading mode will not place real orders even when it receives a valid signal. Check these before anything else:

• Bot status: active or paused
• Daily loss limit: has it been hit for the day
• Max open positions: are you already at the limit
• Paper trading mode: if enabled, orders go to your simulated account, not your broker

Step 4: Check your broker connection

If Signal History shows a trade was attempted but the broker rejected it, you will see a broker-level error in the log. Common causes:

• Your broker OAuth connection expired or was revoked. Re-authenticating in RelayDesk under Settings > Integrations > Broker usually resolves this.
• Insufficient buying power or margin
• Your account lacks the permissions required for that instrument (for example, options trading not enabled on the account)
• Market hours restrictions, where your bot tried to place an order outside the session your broker allows for that instrument

Most issues trace back to three things

After working through hundreds of support cases, the patterns are clear. Missed executions almost always trace back to one of these: