TradingView alert not reaching MT5? A PineConnector troubleshooting guide

When a TradingView alert does not become an MT5 order, first separate receipt from execution. PineConnector can accept and log a webhook while the EA, mapping, broker, or account risk settings stop the final fill.

Check the webhook and message first

• Use the unique webhook URL copied from the dashboard, not a browser page URL.
• Put valid JSON in TradingView's Message field.
• Include symbol and action; strategy alerts should use {{strategy.order.action}}.
• Confirm the action is supported: buy, sell, close, closelong, or closeshort.

If the webhook is logged but not sent

Open the signal or trade log and read the status and error. An expired plan, daily quota, duplicate payload, missing action, or invalid quantity is rejected before the EA can place anything. Identical payloads inside the deduplication window are not sent twice.

Check the MT5 terminal

1. Make sure TV2MT5Bridge.ex5 is attached to a chart and the terminal is logged in.
2. Turn on Algo Trading and allow WebRequest for the exact PineConnector origin.
3. Confirm the EA license key and API base URL match the dashboard account.
4. Wait for a fresh poll and check the connected time on the MT5 account card.

Check broker symbols and stops

A broker may list NAS100 as US100.cash or EURUSD as EURUSD.m. Confirm the mapping against the terminal's Market Watch. Invalid stop distances, volume steps, market closures, and insufficient margin are broker-side rejects, so the log is more useful than repeatedly firing the alert.

Check the account safety controls

A kill switch, max daily trades, drawdown pause, or close-on-reverse setting can change what happens by design. These controls block new entries; they do not silently create a substitute order. Turn them off only after checking the demo behavior and your risk plan.

For the payload format, read the webhook guide. For suffixes, see MT5 symbol mapping. If the EA is not installed yet, follow the PineConnector EA setup guide.