A TradingView-to-MT5 instruction is one short line, and every field in it can be right in your head and wrong at the broker. The symbol you typed is not the symbol your broker lists. The lot size is below the minimum for that instrument. The Licence ID points at a connection you forgot was still attached to a second account. None of these are bugs in a connector. They are mismatches between what you wrote and what the terminal and broker actually accept, and each has a specific place where the truth lives.
This article walks through the four fields of a PineConnector instruction, shows where to check each one before you rely on it, and ends with a pre-flight table you can run on a demo account. It applies to a self-hosted terminal and to managed MT5 hosting with PineConnector Edge alike, because the instruction is the same in both cases. If your alert is already arriving but nothing happens, start with the stage-by-stage diagnosis instead; this article is the checklist for before that point.
The shape of the instruction
PineConnector's syntax documentation gives the format as LicenseID,Command,Symbol,Parameters, with examples such as 60123456789,buy,AUDUSD,vol_lots=0.1 and 60123456789,closelong,GBPUSD.[1] Four fields, separated by commas. The first decides which account is affected, the second what to do, the third on which instrument, and the fourth how much and with what protection. Every example in this article uses the placeholder Licence ID from the documentation and demo-account thinking throughout. No live trade is shown or implied.
Field 1: the Licence ID decides which account acts
The Licence ID is not a password. It is a routing key. PineConnector's FAQ describes the model plainly: "One connection links one MetaTrader account through PineConnector Bridge," and for multi-account setups, "sending an alert to that License ID will replicate the trade instructions to all the connected trading accounts."[2] That second sentence is the one to read twice. If you attached a second terminal to the same licence months ago for a test and never detached it, every alert you send today reaches both.
On PineConnector Edge, the hosted instance is tied to a licence at setup: the Edge Guide's first step is "Select the License ID you would like to use for your Edge connection," followed by "Enter your MT5 account login and password. Select the corresponding broker server."[3] The guide does not describe any conditional routing between instances, so the working assumption is the same as for a self-hosted terminal: the licence in the alert is the licence whose connections act.
Where the truth lives: the connections list in your PineConnector portal, under that licence. How to check: before sending anything, confirm exactly which accounts are connected to the Licence ID you are about to put in the alert, and that each of them is the account you intend. If you run several accounts and want them to behave differently, they need different licences; the multi-account hosting article covers the trade-offs.
Field 2: the command must be spelled the way the documentation spells it
Commands are documented words, not free text. The syntax page lists them, and a close command in the examples is written closelong, one word.[1] A connector cannot guess that close long, Close_Long or exit mean the same thing. When in doubt, copy the command from the documentation rather than typing it from memory, and keep your TradingView alert message templates in one place so a fix in one is a fix in all.
Where the truth lives: docs.pineconnector.com/syntax. How to check: paste your alert message next to the documented example and compare field by field.
Field 3: the symbol is your broker's name for it, not TradingView's
This is the most common mismatch we see, and PineConnector's own documentation is direct about it. The test-alert guide warns that "your broker may have different symbol names configured in MetaTrader. The symbol name might be EURUSD.i or EURUSD.mini" and that "It's important to use the exact symbol name as listed by your broker, taking into account case sensitivity."[4] The FAQ repeats the rule: "The symbols are case-sensitive—for example, EURUSD is NOT the same as eurusd."[2]
Suffixes vary by broker and by account type at the same broker. Indices and crypto are worse than forex, because there is no single convention: the syntax page's own examples include US30.Cash and BTCUSD,[1] but your broker may call the same instruments something else entirely. The TradingView chart you built the strategy on may show a symbol from a data feed that is not your broker at all.
Where the truth lives: the Symbols window in your MetaTrader terminal. PineConnector's test-alert guide points to the Symbol List (Ctrl+U) and tells you to use the name shown in the "Symbol" column exactly.[4] How to check: open that window on the account the licence actually points at, find the instrument, and copy the name character for character into your alert. On Edge, you do not have a terminal window to open, so check the symbol name on the same broker account in any MT5 terminal or the broker's own contract list, then confirm on a demo instance that the test signal is accepted.
Field 4: volume must fit the symbol's rules, not just your risk model
The syntax page lists the sizing parameters and their meanings verbatim: vol_lots= to "Set fixed lot size", vol_dollar= to "Set risk in dollar amount (requires SL)", vol_pct_bal_loss= to "Set risk as % of Balance (requires SL)", vol_pct_eq_loss= to "Set risk as % of Equity (requires SL)", and vol_pct_bal_margin= to "Set volume by % of Balance used as Margin". The three risk-based modes each require a stop loss given as sl_pips=, sl_price= or sl_pct=.[1] An instruction that says "risk one percent" with no stop is not an instruction the connector can size, because there is nothing to size against.
Even a correctly computed size can still be rejected. Every MT5 symbol carries a specification, and MetaQuotes' terminal help defines the three fields that matter here: "Minimal volume — minimal volume of a deal for the symbol", "Maximal volume — maximal volume of a deal for the symbol", and "Volume step — volume change step".[5] A percentage-of-balance calculation on a small demo account can land below the minimum; a fixed lot on an index CFD can violate the step. PineConnector's FAQ says what happens then: "If the target lot size is less than your broker's Minimum Lot or greater than the Maximum Lot for that symbol... we have to reject the order and will state the reason in the MetaTrader 'Experts' log."[2] At the trade server itself, the corresponding return code is 10014, TRADE_RETCODE_INVALID_VOLUME, "Invalid volume in the request", alongside neighbours such as 10019 "There is not enough money to complete the request" and 10018 "Market is closed".[6]
Where the truth lives: the symbol's Specification window in MetaTrader, opened from the Market Watch context menu.[5] How to check: read minimal volume, maximal volume and step for the exact symbol on the exact account, then confirm your sizing mode produces a value inside that range for the balance you actually hold on demo.
One note on where you can see the rejection
On a self-hosted terminal, the Experts log is where PineConnector says it records a volume rejection.[2] On PineConnector Edge, that log is not available today: the Edge Guide states that "Trading account data, including account balance, and the Experts and Journal logs are not yet available," with customisation "planned for a future update."[3] What Edge users have today is the portal Signals Log, which the test-alert guide describes as showing "timestamps indicating when our server received the signal and when the PineConnector EA processed it,"[4] the Bridge page's ability to "send test signals and view their processing results,"[3] and the broker's own trade history. That is supported today; terminal logs on Edge are planned, not available. If reading the Experts log is part of how you work, self-hosting remains the route for now.
Pre-flight table: run it on a demo account
PineConnector recommends exactly this: "We recommend using a demo account for your first setup and test trade," and "Before using live automation, send a test alert from TradingView to a demo account and verify that the expected trade appears in your broker account."[3]
| Field | Where the truth lives | How to check on demo | Healthy looks like |
|---|---|---|---|
| Licence ID | Portal connections list under that licence | Count the connected accounts; detach any you do not intend to trade | Exactly the intended account(s), nothing else |
| Command | docs.pineconnector.com/syntax | Compare your alert text to the documented example word for word | Documented spelling, lower case, no spaces |
| Symbol | MetaTrader Symbols window (Ctrl+U) on that account | Copy the "Symbol" column entry, including any suffix and case | Test signal accepted; order appears on the right instrument |
| Volume | Symbol Specification: minimal, maximal, step | Compute your size for the demo balance; confirm it sits inside the range and on the step | No INVALID_VOLUME; filled volume equals intended volume |
| Stop loss (risk modes) | Syntax page: sl_pips, sl_price or sl_pct required | Send one risk-sized test with a stop and one without; only the first should fill | Stop present on the resulting position |
| Result | Broker trade history; Signals Log; Experts log (self-hosted only) | Verify account, symbol, direction, volume and count of orders | One order, on one intended account, with the expected values |
Run the table again whenever any of the inputs change: a new broker, a new account type at the same broker, a new instrument, or a new sizing mode. Suffixes and specifications differ between live and demo servers at some brokers, so a clean demo run is evidence about that demo server, not a guarantee about live. The nine tests before going live extend this into restart, retry and rejection scenarios.
Frequently asked questions
My TradingView chart says XAUUSD but my broker lists GOLD. Which do I use?
The broker's name, always. The instruction is executed by a terminal logged in to your broker, and it can only find instruments by the names that broker publishes. Check the Symbols window on that account and use the exact string.[4]
Why was my order rejected for volume when my risk percentage was small?
Because a percentage of a small balance can compute to less than the symbol's minimal volume, or to a value that is not a multiple of its step. Read the specification for that symbol and compare.[5] The connector reports the rejection in the Experts log on a self-hosted terminal.[2]
Does the same alert hit all my accounts?
All accounts connected to that Licence ID, yes, according to PineConnector's FAQ.[2] Use separate licences for accounts that should behave differently.
Can I check the symbol and volume on PineConnector Edge before a live test?
You can confirm the symbol name and specification on the same broker account from any MT5 terminal or the broker's contract list, then use the Bridge page's test signals and the Signals Log on a demo instance. Terminal logs on Edge are not available yet.[3]
Next step
Run the pre-flight table on a demo account today. If you are setting up for the first time, the complete TradingView-to-MT5 guide covers both the self-hosted and the PineConnector Edge route and ends with the same verified demo trade.
Reviewed 10 September 2026. Facts were checked against the linked sources on that date.
Sources
- PineConnector Docs – Syntax, accessed 10 September 2026.
- PineConnector Docs – FAQ, accessed 10 September 2026.
- PineConnector Docs – Edge (Early Access) Guide, accessed 10 September 2026.
- PineConnector Docs – Test Alert, accessed 10 September 2026.
- MetaQuotes – MetaTrader 5 Help: Market Watch and symbol Specification, accessed 10 September 2026.
- MetaQuotes – MQL5 Reference: Trade Server Return Codes, accessed 10 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
