Troubleshoot an alert
Find where the alert stopped before changing settings or repeating a trade.
Start with the same alert time and intended account at every stage. A marker on a TradingView chart is not proof that an alert fired, and a received signal is not proof that the broker opened a trade.
Scroll sideways to read the full diagram.
First check the TradingView alert, then the PineConnector message, then the broker’s trade. Investigate the first missing or unexpected result instead of changing unrelated settings.
1. Did TradingView trigger the alert?
Section titled “1. Did TradingView trigger the alert?”Open Alerts → Log and locate the alert at the time of the issue.
- No entry: review whether the alert is active, its symbol/timeframe, condition, trigger frequency and expiration. Check whether TradingView paused it or reported an error.
- An entry exists: open it and inspect the message actually produced. Do not compare only the chart’s strategy markers with MetaTrader’s trade history.
- You changed a script or its inputs: existing alerts retain their saved configuration. Follow the relevant no-code or Pine Script guide and recreate the affected alert where required.
2. Was the webhook configured and delivered?
Section titled “2. Was the webhook configured and delivered?”Open the alert’s Notifications settings. Webhook URL must be checked and its address must match:
Check TradingView’s webhook delivery status or error details where available. An alert notification and successful webhook delivery are different events. Delivery can fail or be delayed; retain the timestamp and reported error instead of assuming the terminal is at fault.
If webhook access is unavailable, check your TradingView plan and two-factor authentication. TradingView webhook help.
3. Does the message identify the right destination?
Section titled “3. Does the message identify the right destination?”Compare the actual message in the alert log with Portal → Connections.
- Use the License ID, not the MT5 account number.
- Check all accounts using that ID, not just the first account you recognise.
- If Signal Authentication is enabled, the message must include the exact matching, case-sensitive
secret=value. - Find the signal by time and account in Bridge or recent signal history. A missing entry alone does not prove a broker execution failure; rejected or misdirected messages need their own checks.
4. Check the message itself
Section titled “4. Check the message itself”The order is License ID → command → broker symbol → parameters. Each message contains one command and one symbol. Use one separate alert message per instruction.
Incorrect field order
Message structure
| Check | Common mismatch |
|---|---|
| Command | A made-up command, or two commands combined into one message. Use the command index. |
| Spelling | rsik instead of risk, or trialtrig instead of trailtrig. |
| Separators | A trailing comma, an extra bracket or explanatory text copied with the instruction. |
| Required fields | No volume for an entry, no entry level for a pending order, or no stop for a sizing method that needs one. |
| Broker symbol | Different capitalisation, prefix or suffix. Review symbol mapping. |
| Comments | More than 20 characters, or an unexpected comment affecting strategy selection. Check the exact label and broker handling. |
Use the builder and message checker for basic structure checks. It cannot verify the account, current market, broker limits, secret or trade outcome.
5. Is the intended MetaTrader environment running?
Section titled “5. Is the intended MetaTrader environment running?”On Edge
Section titled “On Edge”Find the instance in Portal → Edge and check the associated account in Connections. Use Bridge to review the signal’s result. Confirm the broker outcome through the broker’s MT5 interface.
Do not troubleshoot Edge by changing Windows sleep settings on your own computer. Edge runs in the hosted environment. Edge controls and current scope.
On your computer or VPS
Section titled “On your computer or VPS”- MT5 must be running, logged in to the intended broker account and connected to the internet.
- The PineConnector EA must be attached and connected with the intended License ID.
- Algo Trading and the EA’s required permissions must be enabled. Installation checklist.
- Keep the computer awake while it hosts the terminal. Check Windows sleep, restart and network-adapter power-saving settings if the connection drops.
- Read Experts for EA processing details and Journal for the full broker error.
Where to check Windows sleep and adapter settings
- Open Windows power settings. In the source guide’s Windows interface, this is Settings → System → Power & sleep. Set the relevant Sleep option to Never while this computer is responsible for keeping MT5 running. Labels vary by Windows version.
- If disconnections coincide with power saving, open Device Manager → Network adapters, right-click the adapter used for the connection, and select Properties.
- If that adapter exposes a Power Management tab, review Allow the computer to turn off this device to save power. The published guide disables that option for its unattended terminal setup.
- Confirm the terminal stays connected after the relevant idle period. On a managed VPS, check its session and power policies with the provider.
These steps concern the computer hosting MetaTrader. They do not change an Edge-hosted terminal.
An empty “EA Opened” field in older signal-log layouts is not a complete diagnosis. Check whether an account was associated with the signal, then inspect the processing and broker results.
6. The signal arrived, but the result is wrong
Section titled “6. The signal arrived, but the result is wrong”| Symptom | Next check |
|---|---|
| No position, with an error | Read the complete error, including the words beside the number. Error guide. |
| Wrong size or stop | Check parameter units and any legacy EA-setting dependency. Volume and targets. |
| Unexpected duplicate | Check active TradingView alerts, accounts sharing the ID and duplicate EAs in the same terminal. |
| Trades from different strategies interfere | Review strategy separation and the command’s scope. |
| TradingView and broker prices differ | Check the broker’s actual symbol and price feed. Repainting, different data feeds and order timing can affect comparisons. |
On a self-hosted terminal, inspect every chart for accidentally repeated EAs using the same License ID. Keep intentional multi-account setups distinct from duplicate EAs inside one terminal. Review active automation before removing an EA or changing an ID.
Collect useful evidence for support
Section titled “Collect useful evidence for support”For this visit only. Your progress resets when the page reloads.
Open PineConnector Support and explain which checkpoint failed. Share account-specific details only through the support channel when needed; do not post credentials or secrets publicly.
Run a clean demo testUse one alert and a specific expected result to isolate the problem.