Skip to content

Automated trading

Wrong Symbol, Lot Size or Account: Checking the Complete Instruction Before It Reaches Your Broker

A TradingView-to-MT5 instruction can name the wrong recipient, broker symbol or volume even when its format looks correct. Those are checks to perform, not a diagnosis established by the symptom alone. Compare the actual message and broker records before assigning a cause.

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.

Four message checks: recipient License ID, requested action, broker symbol and parameter units.
Verify recipients and units against the receiving setup. A correctly formatted instruction still needs a broker-outcome check.

The shape of the instruction

PineConnector’s documented format is LicenseID,Command,Symbol,Parameters. For example, LicenseID,buy,EURUSD,vol_lots=0.01 is an illustrative entry request, not a recommendation. The destination is the TradingView alert’s Message field. Replace the placeholder with your complete License ID and the symbol with your demo broker’s exact symbol; first confirm every receiving account. [1]

Field 1: the Licence ID decides which account acts

The License ID is a routing value, separate from the broker login. An alert addressed to it can reach every account connected to that ID, not just the account currently open in Portal. Inspect Portal → Connections before sending; do not publish a real ID or account credentials. [2]

On Edge, choose the intended License ID and broker account during setup. The hosted setup follows the same documented routing rule: an alert can reach every account attached to that ID. Confirm the full connection list, including any self-hosted accounts. [3]

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

Use the exact broker symbol, including its suffix and letter case. Copy it from the receiving account, because TradingView’s symbol can differ. The current setup guide gives separate self-hosted and Edge lookup steps. [4]

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 use the Symbols tab (Portal → Edge → Symbols): it lists every symbol the broker offers, searchable, with its specification, and lets you copy the exact name into your alert instead of retyping it (Edge Symbols guide). You can still cross-check the 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 reference defines vol_lots= as lots, vol_dollar= as planned loss in account currency, and vol_pct_bal_loss=/vol_pct_eq_loss= as planned percentage loss at a stop. vol_pct_bal_margin= allocates margin and is not a loss cap. Loss-based methods require one explicit stop method in the same message: sl_pips=, sl_price= or sl_pct=. [1]

Read the symbol’s minimum volume, maximum volume and volume step. PineConnector’s FAQ describes rejecting targets outside the absolute range and rounding in-range targets to the nearest step. The Syntax reference leaves the direction unresolved; verify the calculated, submitted and accepted volume rather than choosing a rounding rule by assumption. Inspect the actual broker response instead of diagnosing every failure as a volume error. [1][2]

For an index CFD such as US30.Cash, use the NAS100 and US30 lot size calculator to check the lot size against the specification you found in MT5.

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

Use Experts for the EA’s calculated/requested volume and Journal for the terminal’s trading messages and broker responses. On self-hosted MT5, open those terminal tabs. On Edge, both hosted logs are available in Portal → Edge. Combine those records with Portal → Bridge / Signals log and broker history; receipt, processing and a broker fill are separate checks. [2][3]

Pre-flight table: run it on a demo account

Use a demo account and check messaging separately from the broker order. The current setup guide provides both stages and requires the actual trade to be verified at the broker. [4]

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 Expected demo fill and resulting position on the intended instrument
Volume Symbol Specification: minimal, maximal, step Compute your size for the demo balance; confirm it sits inside the range and on the step Calculated, requested and filled volumes reconciled with symbol limits
Stop loss (risk modes) Syntax page: sl_pips, sl_price or sl_pct required Review one explicit loss-based message with its required stop; verify actual volume and broker-side stop on demo Stop present on the resulting position
Result Broker trade history; Portal → Bridge / Signals log; Experts/Journal (self-hosted MT5 or Portal → Edge) 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?

A percentage of a small balance can compute below the broker’s minimum volume. In-range values may be rounded to a volume step rather than rejected. Inspect Experts for the requested size and Journal/broker records for the response; on Edge, those hosted logs are in Portal → Edge. [1][2][3]

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?

Yes. The Symbols tab (Portal → Edge → Symbols) lists every symbol the broker offers, with its specification, including minimal volume and volume step, and lets you copy the exact name (Edge Symbols guide). You can also use the broker’s MT5 mobile app, web terminal or desktop terminal for the same account, and ask the broker for any value the tab does not show. Then follow the demo setup test and inspect Portal → Bridge / Signals log, Portal → Edge’s Experts/Journal logs and the account outcome. [3][4]

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

  1. PineConnector Docs – Syntax, accessed 23 September 2026.
  2. PineConnector Docs – FAQ, accessed 23 September 2026.
  3. PineConnector Docs – Connect your MT5 account, accessed 23 September 2026.
  4. PineConnector Docs – Test Alert, accessed 23 September 2026.
  5. MetaQuotes – MetaTrader 5 Help: Market Watch and symbol Specification, accessed 10 September 2026.
  6. 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.

Corrections reviewed 23 September 2026 against the cited primary documentation accessed on that date. No trading account was tested and no Pine Script or MQL5 code was compiled for this update.

Back to PiCo Blog

Run your strategies on our managed infrastructure

Bridge routes TradingView alerts to MetaTrader. Edge hosts and runs MT5 for you.

Core Trial

Then $59/month unless you cancel.

$7for 7 days

  • 3 account connections
  • 1 hosted MT5
  • Unlimited alerts, routed by Bridge
Try Core for $7

Trusted by 66,000+ traders in 156 countries and territories · <1s typical latency

Your Edge MT5 runs in our cloud · nothing to install · built on Microsoft Azure