PineConnector Not Working? A Stage-by-Stage Troubleshooting Guide

When PineConnector is not working, the cause is almost always in one of five places: the TradingView alert, the webhook delivery, the alert message, the MetaTrader terminal, or the broker's response to the order. PineConnector's own troubleshooting guide checks them in that order and asks you to compare the same alert time at each stage until one of them shows something missing or unexpected, which is also the fastest way to find the fault.

This page follows the same route and points to PineConnector's documentation at each step. Their docs are the authority on how their EA behaves. If you work through every check and still cannot get your alerts to trade, you can always try PineHook, the TradingView-to-MT5 bridge we build, where we have spent a great deal of time making problems like these quick to diagnose. The last section explains how it handles each of them.

1. Did the TradingView alert trigger?#

Open Alerts → Log in TradingView and find the time you expected the trade. If there is no entry, the alert never fired and nothing after it ran, so check that the alert is still active, has not expired, and uses the symbol, timeframe and condition you intended.

Two TradingView rules catch PineConnector users often. An alert that triggers more than 15 times in 3 minutes is stopped by TradingView, and PineConnector's FAQ lists "triggered too often" among the messages to look for. An alert also keeps the version of the script it was created with, so after editing a strategy you need to delete and recreate the alert, and our guide to TradingView alerts not firing covers the remaining causes.

2. Did the webhook reach PineConnector?#

If the alert fired, check its Webhook status in the same log, where a failed delivery means TradingView could not complete the request. TradingView requires two-factor authentication for webhook alerts and a plan that includes webhooks, so confirm both, then copy the webhook URL again from PineConnector's portal rather than retyping it and make sure the Webhook URL option is ticked in the alert's Notifications tab. Our guide to TradingView webhook error codes explains what each delivery status means.

3. Is the alert going to the right License ID?#

PineConnector routes alerts by the License ID at the start of the message rather than by your MT5 account number. Their missing signals guide warns against putting the broker login in that position, and their EA settings reference notes that alerts sent to a shared License ID can reach every account attached to it. If a trade appeared on the wrong account, or on two accounts at once, check which terminals use that ID.

If you have turned on PineConnector's Signal Authentication, every alert also needs the matching secret= value, and their syntax guide says the value is case-sensitive and that a missing or different value stops the alert from reaching the terminal.

4. Is the PineConnector alert syntax valid?#

PineConnector's syntax guide sets out the rules, and these are the ones that trip people up most:

• The order is fixed: License ID first, then the command, then the symbol, then parameters written as name=value, and swapping the command and the symbol is a mistake their docs call out specifically.
• The symbol must be the broker's exact name, including any suffix and letter case, and while PineConnector's EA offers Symbol Prefix and Suffix inputs alongside a separate Symbol Mapping feature in the portal, their docs warn against adding the same prefix in more than one of those places.
• Each entry needs a volume method, and loss-based sizing also needs a stop in the same message.
• A parameter you leave out is not treated as zero or as a default.
• comment= is limited to 20 characters and should not contain commas. Commas separate the fields.

Misspelled parameter names are easy to overlook. Placeholders also change the text at trigger time, so read the message TradingView actually sent, as shown in the alert log, rather than the template you wrote.

5. Is the MT5 terminal ready to trade?#

For a self-hosted setup, PineConnector's checklist asks for MT5 to be running, logged in and online, with their EA attached, Algo Trading enabled and the computer kept awake. Their EA also needs DLL imports allowed, and their FAQ states that the current MT5 guide does not require a WebRequest URL, so read the Experts and Journal tabs at the alert time for anything the EA printed.

If you use PineConnector's hosted Edge terminals, your local settings do not apply. Their error guide notes that changing Algo Trading on your own computer does not affect Edge, and that applying Edge EA settings restarts the terminal, which interrupts execution until the restart finishes.

6. What did the broker say?#

When the alert reached the terminal and no position opened, the Experts tab carries an error, and PineConnector's error guide lists the MT5 ones. These are the most common:

The 4756 code itself only says that a request failed, while the message beside it carries the reason, and our guide to MT5 error 4756 explains how to read it. On MT4, the codes are different, and their guide lists 4109 for disabled automated trading and 4017 for DLL calls not allowed.

When to contact PineConnector support#

If every stage checks out and the trade still did not happen, collect the alert time, the message TradingView sent, the Signal ID shown under Connections → Log in PineConnector's portal, and the Experts and Journal lines for that moment. Their error guide asks for the same details, and having them ready makes the conversation much shorter.

Still not working? Try PineHook#

Most of the causes above are configuration problems that any TradingView-to-MT5 tool shares, so switching tools will not fix a wrong symbol or a disabled Algo Trading button by itself. Where tools differ is in how quickly they tell you which stage failed and why, and that is the part PineHook was built around.

Every alert sent to PineHook lands on a row in Signal Logs that ends in a written answer, whether it executed, which of your own settings blocked it, or what the broker objected to. A refused stop, for example, reads as SL distance 0.00008 is below broker minimum 0.00015 rather than a bare 4756. A malformed alert appears in the Rejected panel with the faulty parameter highlighted and a sentence explaining the fix, and Test EA Connection checks the route to MT5 and its Algo Trading permissions without placing a trade.

If you decide to try it, PineHook has a PineConnector compatibility mode that accepts PineConnector-style alerts once you swap the license ID and webhook URL, and our PineConnector alternative page compares the two products in detail. Unit settings such as what risk= means have to match your old setup, so create a PineHook account without payment details and test your existing alerts on a demo account first.

FAQ#

Why is PineConnector not executing trades when the alert fired?

Check the stages after the trigger in order: the webhook status in TradingView's log, the License ID and syntax of the message, whether the MT5 terminal is running with Algo Trading on, and finally the broker error in the Experts tab.

Does PineConnector need a WebRequest URL in MT5?

PineConnector's FAQ states that its current MT5 guide does not require a WebRequest URL, so if an older guide told you to add one, follow their current documentation instead.

Can I use my PineConnector alerts with another bridge?

Only with a bridge that understands their syntax. PineHook's compatibility mode accepts PineConnector-style alerts after you change the license ID and webhook URL, though you should test them on a demo account first because unit settings must match.

Related guides#

• TradingView alert not firing
• MT5 error 4756 trade request sending failed
• PineConnector compatibility mode
• PineConnector alternative

PineConnector, MetaTrader and TradingView are trademarks of their respective owners, and PineHook is an independent product that is not affiliated with, endorsed by, or sponsored by any of them. Leveraged trading carries a high risk of loss, so test any automated setup on a demo account before you trade it live.