Troubleshooting
Quick fixes for the most common issues we see in support.
Alert fires, no execution
Check Bridge → Logs. No row → wrong webhook URL or secret. Row with rejected + no_terminal → MT5 was offline; keep the EA running and resend. Row with rejected + other reason → see the reject_reason column.
MT5 offline
Signals are not queued while offline. You'll get a throttled email and an entry in the terminal activity feed. Fix the EA connection, wait for online status, then resend from TradingView.
Wrong symbol
Add or fix symbol mapping on the terminal. Ensure the symbol row exists, lot mode is set, and the symbol is active.
Broker rejects
Broker rejections show in Bridge logs with the raw MT5 message — common causes: market closed, invalid volume, or symbol not tradable.
Unexpected latency
Median ingest-to-ACK is ~184 ms. Spikes may come from broker latency or TradingView delivery delay on free plans. See Analytics for percentiles.
Related guides
Want to contribute?
Spot an inaccuracy or missing detail? Send us a note from the contact page — real humans read every message.