Troubleshooting
Find fixes for PineHook connection issues, missing TradingView webhook alerts, rejected signals, and failed trades on MT5 or cTrader.
Last updated: 2026-10-08
These guides help you find the cause when your account will not connect, an alert goes missing, or a trade fails. Choose the issue that matches what you are seeing below, then follow the checks for your MT5 or cTrader account.
Find your issue#
License disconnected
MT5
Open View → Toolbox → Experts in MT5 and use the connection error to check DLL permissions, the license key, or any required Secret Key.
Fix an MT5 connectioncTrader
Check the status beside the license to see whether you need to link a broker account or renew its cTrader authorization.
Fix a cTrader connection
Alert missing
Check whether the alert triggered
Open TradingView's Alerts → Log to see whether the alert triggered. If it did not, check that its condition was met and that the alert is active and has not expired.
Check the TradingView triggerCheck delivery
If the alert triggered, inspect Webhook status in TradingView's alert log, then verify the webhook URL and the license key in your message.
Find a missing webhook
Alert rejected or blocked
Follow the reported reason
For a parse error, open Signal Logs → Alert Test & Validate in your dashboard, paste the corrected message, and select Check alert to validate it without placing a trade. If the alert was blocked, check the authentication, filter, or risk setting named in the log.
Resolve a blocked alertCheck duplicate delivery
A duplicate badge means PineHook stopped an identical message that arrived again. Include a unique id= in each new alert, keeping the original ID if that same alert is retried.
Set up alert IDs
Trade failed
Open the execution error
Open the alert in Signal Logs and use its execution error to find the relevant fix for broker symbols, volume, margin, prices, stops, or trading permissions.
Find the trade-error fix
Unexpected trade result
Compare the message and effective settings
Compare the message PineHook received with the destination settings, including syntax mode, settings source, copier multiplier, symbol mapping, and lot conversion.
Check the trade settings
License disconnected
MT5 or cTrader has no active connection.
MT5. Open View → Toolbox → Experts in MT5 and use the connection error to check DLL permissions, the license key, or any required Secret Key.
Fix an MT5 connectioncTrader. Check the status beside the license to see whether you need to link a broker account or renew its cTrader authorization.
Fix a cTrader connection
Alert missing
No matching alert appears in Signal Logs.
Check whether the alert triggered. Open TradingView's Alerts → Log to see whether the alert triggered. If it did not, check that its condition was met and that the alert is active and has not expired.
Check the TradingView triggerCheck delivery. If the alert triggered, inspect Webhook status in TradingView's alert log, then verify the webhook URL and the license key in your message.
Find a missing webhook
Alert rejected or blocked
PineHook received the message but stopped it.
Follow the reported reason. For a parse error, open Signal Logs → Alert Test & Validate in your dashboard, paste the corrected message, and select Check alert to validate it without placing a trade. If the alert was blocked, check the authentication, filter, or risk setting named in the log.
Resolve a blocked alertCheck duplicate delivery. A duplicate badge means PineHook stopped an identical message that arrived again. Include a unique id= in each new alert, keeping the original ID if that same alert is retried.
Set up alert IDs
Trade failed
Execution failed on MT5 or cTrader.
Open the execution error. Open the alert in Signal Logs and use its execution error to find the relevant fix for broker symbols, volume, margin, prices, stops, or trading permissions.
Find the trade-error fix
Unexpected trade result
The size, symbol, stop, or target differs from your intent.
Compare the message and effective settings. Compare the message PineHook received with the destination settings, including syntax mode, settings source, copier multiplier, symbol mapping, and lot conversion.
Check the trade settings
Reading Signal Logs status#
| Status | What to do |
|---|---|
| EXEC | Execution was confirmed, so if the result differs from what you expected, compare the alert parameters with the account settings. |
| RECV or SENT | Delivery or execution confirmation is still pending. If the status does not change, check the license connection and platform logs. |
| DLYD | The alert is waiting for its scheduled delay, so check when it is due to run. |
| RJCT | Correct the message format or parameter named in the error. |
| BLCK | Read the reason, then check the corresponding authentication, filter, risk management, or account-limit setting. |
| BLKD | An older status for duplicates that PineHook no longer creates. Today an identical alert arriving again within 12 seconds is dropped without a new row. Give each alert a unique id= so separate alerts are never mistaken for a resend. |
| FAIL | Read the execution error and use Trade Errors. |
| ABDN | The alert will not execute because it was abandoned. Open its details to find the reason. |
For the full log controls, see Signal Logs.
Where to find the error#
In Dashboard → Signal Logs, open the alert's row to read its status and any rejection or execution error. If there is no matching row, check TradingView's Alerts → Log → Webhook status and follow Alerts Not Received to trace its delivery.
For MT5 connection or execution problems, View → Toolbox → Experts contains PineHook messages, while Journal records terminal and DLL errors. On cTrader, check the license's authorization status alongside the broker account assigned to it.
Getting help#
If the checks do not resolve the issue, ask the Support Chatbot about the error or to open a support ticket. Include the platform, license ID, exact error, alert time, and checks you tried, with passwords and Secret Keys removed from any messages or screenshots.