Troubleshooting Missing Signals
We are, however, preparing to launch PineConnector Echo, which will scan your TradingView Alerts Log to detect missed signals and internally generate them so that your trading can continue with minimal disruption.
Diagnosing Missing Signals: A Step-by-Step Guide
If you encounter issues with missing signals, follow these steps to diagnose and resolve the problem:
1. Ensure Persistent Internet Connection
Maintaining a stable internet connection is crucial for the proper functioning of MetaTrader and PineConnector. Here are some steps to ensure a persistent internet connection:
- Verify Connection Stability: Ensure that MetaTrader is successfully running PineConnector with a stable connection.
- Prevent Sleep Mode Interruptions: If your laptop or computer goes into sleep mode, the internet connection might get interrupted. Ensure your device does not enter sleep mode while running MetaTrader.
- High Power Mode: Configure your Windows operating system to run in high power mode to prevent interruptions. Follow these steps:
- Open Control Panel: Search for and open the Control Panel from the Start menu.
- Select Power Options: Navigate to Hardware and Sound > Power Options.
- Choose or Customize a Power Plan: Select “High Performance” or customize a power plan to ensure the internet connection is not interrupted.
- Additional Windows Recommendations:
- Disable Sleep Mode:
- Go to Settings > System > Power & sleep.
- Set “Sleep” to “Never” for both battery and plugged-in modes.
- Disable Network Adapter Power Saving:
- Go to Device Manager > Network adapters.
- Right-click your network adapter, select Properties.
- Under the Power Management tab, uncheck “Allow the computer to turn off this device to save power.”
By following these steps, you can ensure that MetaTrader has a persistent internet connection, which is essential for receiving signals from PineConnector without interruptions.
2. Check TradingView Alert Activation
Confirm that the alert was triggered by reviewing your TradingView alerts log. A new entry should be visible indicating the alert was activated.
3. Confirm Webhook URL
Confirm the webhook link used in your alerts matches the following URL exactly.
For PineConnector v3:
https://webhook.pineconnector.com
For PineConnector v2:
https://pineconnector.net/webhook/
On the pop-up, click “Notifications” and you will be able to see the Webhool URL used.
4. Verify Alert Message Compliance
Please ensure the alert message is PineConnector-compliant by referring to the checklist below. This will help verify that the format and syntax meet the required standards and allow you to address any potential issues or errors.
4.1. Incorrect License ID
Ensure that your alert message contains your correct License ID.
4.2. Incorrect Syntax Format
Incorrect Order
LicenseID,EURUSD,buy,risk=1 (not acceptable)
LicenseID,buy,EURUSD,risk=1 (acceptable)
Multiple Commands
LicenseID,closelong,EURUSD,buy,GBPUSD,risk=1 (not acceptable)
LicenseID,closelong,EURUSD (acceptable - sent separately)
LicenseID,buy,GBPUSD,risk=1 (acceptable - sent separately)
4.3. Incorrect Syntax Command
Ensure command used is one of those listed in the Syntax page.
LicenseID,closesome,EURUSD,risk=1 (not acceptable)
LicenseID,closelongpct,EURUSD,risk=1 (acceptable)
4.4. Misspelling
A command or component is spelled incorrectly — commonly “risk” and “trail” are misspelled.
LicenseID,buy,EURUSD,rsik=1 (not acceptable)
LicenseID,buy,EURUSD,risk=1 (acceptable)
LicenseID,buy,EURUSD,risk=1,trialtrig=10,trialdist=8,trialstep=5 (not acceptable)
LicenseID,buy,EURUSD,risk=1,trailtrig=10,traildist=8,trailstep=5 (acceptable)
4.5. Accidental Inclusions
Inclusions such as brackets — especially when using dynamic codes or placeholders.
LicenseID,buy,EURUSD,risk=1,sl=5} (not acceptable)
LicenseID,buy,EURUSD,risk=1,sl=5, (not acceptable)
LicenseID,buy,EURUSD,risk=1,sl=5 (acceptable)
Copy the v3 webhook address below, if needed:
https://webhook.pineconnector.com
4.6. Excessive Comment Length
The comment length exceeds the permissible limit — it can be no more than 20 characters.
LicenseID,buy,EURUSD,risk=1,comment=12345678901234567890 (valid, within 20 charactes)
LicenseID,buy,EURUSD,risk=1,comment=123456789012345678901 (invalid, above 20 charactes)
EA Opened Blank
When signals are received where you are able to see them in your Signal Log but the EA Opened column remains blank, consider the following possibilities:
1. Account Number Absent
License ID Not Running If the account number is absent, it indicates that no trading account is associated with that License ID.
In this case, ensure PineConnector EA v3.13 or later is operational on your MT4/5 terminal using the correct License ID.
2. Account Number Visible
Check Experts Tab If the account number is visible but EA Opened remains blank, examine the Experts tab on your MT4/5 terminal for error messages or alerts that could explain the issue.
On this page
- Troubleshooting Missing Signals
- Diagnosing Missing Signals: A Step-by-Step Guide
- 1. Ensure Persistent Internet Connection
- 2. Check TradingView Alert Activation
- 3. Confirm Webhook URL
- 4. Verify Alert Message Compliance
- 4.1. Incorrect License ID
- 4.2. Incorrect Syntax Format
- 4.3. Incorrect Syntax Command
- 4.4. Misspelling
- 4.5. Accidental Inclusions
- 4.6. Excessive Comment Length
- EA Opened Blank
- 1. Account Number Absent
- 2. Account Number Visible