Test your setup

Your account should now be connected, with its License ID copied from Edge setup. This stage checks connection messaging first, then follows one demo order from TradingView to the broker.

Check	What it establishes
Connection test	Whether the fixed test message reaches the connected setup and produces the expected processing record.
TradingView demo order	Whether the alert condition, message, webhook, routing and broker order work together.

1. Check connection messaging

Paste the copied License ID, review the fixed LicenseID,test,test message and select Send connection test once.

Send a connection test

Check the connection using the fixed message below.

Open Portal → Bridge and look for the matching test by time and account. Inspect its processing result. A browser response saying sent or accepted does not, by itself, confirm that the terminal processed it.

If the browser cannot confirm delivery, check Bridge before trying again. If the connection test needs investigation, use Missing signals or EA Errors.

This check does not verify a broker trade or TradingView’s configuration. Continue with the separate order test below.

2. Find the broker symbol and prepare the message

This next check requests a trade

Use a demo account. A buy message can place a real-money order if it reaches a live account. Check every account sharing the selected License ID before creating the alert.

Use your broker's exact symbol

Your broker may list EURUSD, EURUSD.i or EURUSD.mini. Use the complete name exactly, including capitalisation, prefix and suffix. The name on your TradingView chart is not automatically the broker’s order symbol.

On Edge: find the symbol in the broker’s supported MT5 mobile app, web terminal or desktop terminal for that same account. On a self-hosted desktop terminal: press Ctrl+U and read the Symbol column.

Enlarge

Desktop MT5 example: use the Symbol column, not the longer description. Your broker may use a different name.

Desktop MT5 example: use the Symbol column, not the longer description. Your broker may use a different name.Open original Close Esc

Check the instrument’s permitted lot size and trading session. It must be open for trading when you expect the demo order. If your broker’s EURUSD market is closed, wait or use another open demo instrument whose exact name and permitted size you have checked.

This example requests a buy of 0.01 lots on EURUSD, without SL or TP. Replace the License ID and broker symbol. Change 0.01 only if your demo account requires a different permitted volume.

Demo buy message

TradingView → Message PineConnector Syntax

LicenseID,buy,EURUSD,vol_lots=0.01

If Signal Authentication is enabled, use the form below and replace YOUR_SECRET privately in TradingView. Never put the secret into the docs’ License ID field or connection-test tool.

Demo buy with authentication

TradingView → Message PineConnector Syntax

LicenseID,buy,EURUSD,vol_lots=0.01,secret=YOUR_SECRET

3. Open TradingView’s alert editor

1. Open a normal price chart receiving live, positive quotes, such as a liquid BTCUSD chart.
2. Select the Alerts alarm-clock icon in the right-hand toolbar.
3. Select + or Create alert. You can also use Alt + A on Windows or Option + A on Mac.

Enlarge

Open Alerts, then use + or Create alert to make the temporary test.

Open Alerts, then use + or Create alert to make the temporary test.Open original Close Esc

The trigger chart and the order symbol are separate. A BTCUSD chart can trigger the fixed EURUSD message above. Keep the broker symbol in the message; do not replace it with a chart-ticker placeholder for this test.

A 24/7 chart can receive quotes while your broker’s EURUSD session is closed. You need both a working trigger chart and an open broker trading session to expect the complete demo test to finish.

4. Configure the temporary alert

Settings: Greater Than 0, only once

Set these fields in Settings:

Field	Value for this test
Condition	Price
Operator	Greater Than
Value	0
Trigger	Only Once; some layouts call this Once only

Enlarge

Use Greater Than 0 and Only Once. This original screenshot shows the intended condition and frequency.

Use Greater Than 0 and Only Once. This original screenshot shows the intended condition and frequency.Open original Close Esc

With a positive live quote, the condition is already satisfied, so the test should trigger on the next eligible price update. It is not a guarantee of an instant notification: no incoming quote, a closed chart session or delivery delays can prevent an immediate result.

Choose Greater Than here. Crossing waits for the price to cross the level and is unsuitable for this zero-threshold test. Keep this as a temporary setup test, not a strategy condition. TradingView explains its operators and one-time price-alert frequency.

Message: paste the reviewed buy instruction

1. Open Message. Depending on your TradingView layout, this is a tab or a button opening Edit message.
2. Name the alert Demo trade test so you can find it later.
3. Paste your complete reviewed buy message into Message.
4. If the editor has an Apply button, select it to return to the alert settings.

Enlarge

Paste your message in the Message field. Replace the placeholder; the example image does not supply your License ID.

Paste your message in the Message field. Replace the placeholder; the example image does not supply your License ID.Open original Close Esc

Before continuing, read the actual message: correct License ID → buy → exact broker symbol → intended volume. Add the matching authentication secret only if it is enabled.

Notifications: enable the webhook

Open Notifications, tick Webhook URL, and paste this address:

PineConnector webhook URL

The webhook goes in Notifications; the trading instruction stays in Message.

Enlarge

Both the Webhook URL checkbox and the correct address are required. Other notification channels are optional.

Both the Webhook URL checkbox and the correct address are required. Other notification channels are optional.Open original Close Esc

Select Apply if your layout uses it. Webhook access must be available on your TradingView plan and two-factor authentication must be enabled.

Review and create

Recheck the demo account group, exact message, Greater Than 0, Only Once and webhook URL. Then select Create once.

Keep one trade-test alert active. Do not create several copies while waiting for a result; a later trigger could produce extra orders.

5. Check TradingView’s Alerts log

Open Alerts → Log and find Demo trade test. Confirm its time and the actual message that fired.

Enlarge

Use the Log tab and match your test name/time. The historical message is hidden in this source-derived image; inspect your own message.

Use the Log tab and match your test name/time. The historical message is hidden in this source-derived image; inspect your own message.Open original Close Esc

A one-time alert stops after it fires. If you see Stopped — Triggered, that can be the expected one-time state, not a failure.

If no event appears, first check that the chart is receiving live positive quotes and that the operator and trigger are correct. TradingView has not sent the message merely because you clicked Create.

6. Confirm processing in Bridge

1. Open PineConnector Portal → Bridge.
2. Find the new entry using the alert time and intended account.
3. Open its details and compare the message, symbol, action and processing result.

Enlarge

Bridge layout example with historical Closelong records. Your buy test must match your own new BUY message and account, not these sample rows.

Bridge layout example with historical Closelong records. Your buy test must match your own new BUY message and account, not these sample rows.Open original Close Esc

If the message is missing or rejected, follow Missing signals or the matching EA error. A successful processing record is one checkpoint; still confirm the actual trade at the broker.

7. Confirm the trade in the broker account

Open the same broker account in its supported MT5 mobile app, web terminal or desktop terminal. Open its Trade/positions view. On desktop MT5, the Trade tab is in the lower Toolbox panel.

Check	Expected for the unchanged example
Account	The intended demo account, not another account sharing the ID.
Symbol	The exact broker symbol you put in the message.
Direction	Buy.
Volume	0.01 lots, unless you deliberately changed it to a permitted value.
SL / TP	None from this test message.
Duplicates	No unexpected additional order.

Enlarge

Historical desktop trade view with private/example values hidden. Read your own Volume column: it should show 0.01 for the unchanged test. Enlarge to inspect the column labels; mobile and web layouts differ.

Historical desktop trade view with private/example values hidden. Read your own Volume column: it should show 0.01 for the unchanged test. Enlarge to inspect the column labels; mobile and web layouts differ.Open original Close Esc

If an order is missing, inspect Experts and Journal at the matching time. On Edge, select your instance in Portal → Edge to read both logs in your browser. For a self-hosted terminal, open the tabs in MT5. Check the intended broker account’s positions and history before repeating a trading command.

Before retrying, check the account for an existing order. A delayed notification is not proof that the first request failed.

8. Finish the test

Close the demo position through your broker interface, then disable or delete the temporary TradingView alert.

You are ready for the next stage when the intended TradingView alert was matched to its processing record and the expected broker trade, with no unintended duplicate.

Next · Step 4 of 4Connect your strategy

Optional reference

Additional checks

Can I send the connection-test message from TradingView instead?

Yes. Follow the same one-time alert procedure above, using the message below instead of the buy message. Name it Connection test.

Connection-test message

TradingView → Message PineConnector Syntax

LicenseID,test,test

Match the event in TradingView and Bridge, then remove the temporary alert. This checks message delivery from TradingView; it does not verify a broker order.

Link to this answer