TradingView Webhook Not Working? Step-by-Step Fixes

TradingView webhook not working? Start in the alert log. Find the event, read its Webhook status, locate the corresponding PickMyTrade alert, and check the broker order. That sequence tells you whether to fix the trigger, delivery, message, or account configuration. Change the setting tied to the evidence, then test again.

This troubleshooting guide covers PickMyTrade connections including Rithmic, ProjectX, Interactive Brokers, TradeLocker, cTrader, Match-Trader, TradeStation, Tradier, and Ironbeam. The checks apply across the signal path, while message formats and broker controls depend on the connection. Keep that broker-specific guide open alongside this checklist.

Key takeaways

• Check the TradingView event, webhook delivery, PickMyTrade receipt, and broker outcome separately.
• TradingView requires two-factor authentication and cancels webhook requests exceeding three seconds.
• Use the current generated URL and the appropriate message for your connection.
• Inspect existing orders before retrying, then test both entry and exit in demo.

TradingView webhook not working? Find the failed stage first

Follow the records in order. A TradingView event confirms the alert triggered; the delivery status shows the webhook outcome. Next, use the PickMyTrade Alerts section to inspect receipt and processing. Finally, review the broker order and position to determine whether the trade filled.

Hypothetical example: a 10:15 TradingView event shows successful delivery, while PickMyTrade records a symbol-mapping error. No broker order exists. Fix the mapping indicated by that received message, then run a controlled test. Replacing the webhook URL would address a different stage and leave the documented mismatch unresolved.

1. Did the TradingView alert actually trigger?

In TradingView, open the Alerts panel and select Log. Find the expected event by alert name and time, then read Webhook status. If the column is hidden, check the log’s display options. TradingView’s alert-management guide explains the manager and log controls.

No event at the expected time? Check the individual alert’s active status, expiration, condition, symbol, and timeframe. Confirm that the condition actually occurred after activation. A marker in historical strategy results doesn’t mean a realtime alert was sent. Use the alert’s own record rather than a chart marker as your starting evidence.

Review the trigger behavior available for that alert type. A bar-close condition waits for the bar to finish, while an alert configured to trigger only once stops after that event. Strategy order-fill alerts and scripted alerts behave differently from simple price alerts. Avoid applying price-alert frequency settings to every strategy alert.

If you changed strategy inputs or code, remember that an existing strategy alert retains its saved copy. TradingView’s strategy alert documentation directs users to delete and recreate the alert to capture changed settings. Plan the replacement around open positions and working orders so you preserve any required exit signals.

2. Are webhook notifications enabled and available?

Edit the affected alert and open Notifications. Confirm that Webhook URL is enabled and populated. If the control is unavailable, check current feature access and account security. TradingView’s webhook documentation requires two-factor authentication. An app or email notification can work even when no webhook is configured.

Recheck the same alert after any account or notification change. Compare its destination and message with the current setup rather than copying from an unrelated working alert. Save the corrected settings, then monitor the next qualifying event. Correcting a field doesn’t retroactively resend an earlier failed webhook.

3. Is the webhook URL correct for this PickMyTrade setup?

Copy the destination from the current setup in PickMyTrade and compare it with the alert’s Webhook URL field. Use the full generated value without extra spaces or manual endpoint substitutions. The PickMyTrade alert setup guide shows the URL and message-copying workflow.

Confirm that you are checking the same PickMyTrade account and broker connection used to generate the alert. This article concerns pickmytrade.io. If you are following a Tradovate tutorial from pickmytrade.trade, switch to the documentation for your actual connection before copying configuration. Don’t infer compatibility from a similar-looking message.

If a token or other authentication value changed, check every affected message and destination field against the current generated configuration. Don’t assume the token appears in the same place for every integration. Keep broker passwords out of the message and redact webhook credentials before sharing logs or screenshots.

4. What does the Webhook status error mean?

Read the complete Webhook status error and keep the timestamp. TradingView’s error reference distinguishes redirects, client errors, server failures, and connection problems. A status category narrows your search; the exact code and service response identify what to investigate next.

For custom middleware, TradingView accepts ports 80 and 443, doesn’t currently support IPv6 webhooks, and cancels requests taking longer than three seconds. These are delivery constraints, not broker-fill deadlines. A trader using PickMyTrade’s generated endpoint should report persistent endpoint failures rather than trying arbitrary port or certificate changes.

5. Is the actual outgoing message valid?

Inspect what the alert actually sends. For the standard generated-message workflow, paste the appropriate PickMyTrade JSON into Message. For a custom Pine script using alert(), inspect the message built by the script. The default text shown in the alert dialog may not represent that script-generated outgoing payload.

Check double quotes, commas, braces, field names, numeric values, and unresolved placeholders. A message can be valid JSON yet contain the wrong account or quantity. Conversely, single-quoted Python-style dictionaries are not valid JSON. TradingView sends valid JSON as application/json and other message text as text/plain.

TradingView’s alerts FAQ distinguishes order-fill messages from scripted alert() calls. Don’t assume a placeholder inside a custom script string will be replaced as though it were in an order-fill template. Compare the received values with the expected values, then correct the specific message-building route.

Choose your connection in the PickMyTrade documentation directory, then open its strategy or indicator setup guide. Rithmic users can use the Rithmic JSON reference. Use the event selection and payload format documented for that route. Don’t transfer broker-specific fields into another integration by assumption.

6. Delivered successfully, but no PickMyTrade alert appears?

In PickMyTrade, open Alerts and expand the date range to include the TradingView event. Compare timestamps with their timezones, then match the connection, symbol, and side. A successful delivery response still needs a matching account record before you can trace processing or execution.

Read the matching row’s Alert Status and retain any available entry or order IDs. Use the Download control when you need an export for support. If the row remains missing, compare the destination and account configuration, then send the delivery record and redacted message for investigation. Don’t assume a missing visible row identifies one specific cause.

7. Did PickMyTrade reject the instruction?

If the alert appears in PickMyTrade, read its full Alert Status before editing the TradingView webhook. The PickMyTrade error reference documents mapping, account-selection, trading-window, and connection-specific issues. Match the exact reported problem with the configuration involved rather than applying unrelated fixes.

• Symbol Mapping Not Found: compare the incoming symbol with the required broker instrument and symbol settings.
• Account ID not found: confirm the currently connected account and regenerate the message with the intended destination selected.
• Trading paused or outside the allowed window: inspect the relevant trading-time settings. Preserve your intended restrictions.
• Connection-specific bracket or permission error: use the guide for that broker and account environment.

For futures, compare contract expiry and broker mapping with the symbol actually received. For stocks, forex, and options, check the exact instrument fields required by the connection. Correct the mismatch that the records reveal. Keep intended risk limits and trading windows in place while diagnosing the problem.

8. Was the broker order rejected, working, or filled?

Open the broker’s orders view and search for the relevant order ID or event. Read its current status and fill details. A working limit order may be waiting for price, while a rejected order needs its rejection reason addressed. Also check cancelled and partially filled orders before placing another instruction.

Confirm the intended demo or live environment, authorization, instrument permissions, session availability, and account limits. Interactive Brokers users should also follow their connection guide for TWS or Gateway requirements. Keep the broker’s complete error message; the same short phrase can reflect different account or permission issues across platforms.

If the broker reports a size rejection, compare the submitted quantity with your configured size and any applicable account multiplier. For example, two contracts with a multiplier of three would imply six contracts if that route applies the multiplier. This is a hypothetical calculation; verify your integration’s actual sizing behavior.

How should you retry a failed TradingView webhook?

Check existing orders and positions before retrying. A timeout doesn’t prove that the receiver performed no action. TradingView’s resubmission policy specifies retries for HTTP 500–599 responses except 504: up to three resends, spaced five seconds apart. Don’t assume every error receives automatic retries.

After fixing the identified cause, use a controlled demo test of the intended configuration. Confirm one qualifying entry, the expected size, the exit behavior, and the final account state. Repeated manual resends can complicate the investigation or produce duplicate exposure. Changing the production timeframe to force a trigger also changes what you are testing.

If your strategy has an open trade, plan how it will exit before stopping or replacing its alert. Disabling an alert doesn’t itself close the external position or cancel submitted broker orders. Review protective orders and outstanding requests as part of the recovery process.

TradingView webhook not working: recovery checklist

Use this checklist after you have identified the failed stage. Keep the production settings recorded and make one relevant correction at a time. Then verify the resulting event through to the broker. A demo check should use the route and behavior you intend to trade.

1. Record the failed event’s timestamp, timezone, and exact status.
2. Confirm the alert is active and its webhook notification is enabled.
3. Match the generated destination and intended broker account.
4. Identify the message route and inspect the actual outgoing payload.
5. Resolve the reported mapping, account, session, or broker error.
6. Check open positions, working orders, and possible retries before resending.
7. Test one intended entry and exit in demo; verify quantity and final account state.

What should you send PickMyTrade support?

Send the evidence needed to match a single event across the systems: timestamp with timezone, TradingView alert name and Webhook status, broker connection, account environment, PickMyTrade status, and any broker order ID. Include the complete error text. Describe the expected action and what actually happened.

Use the authenticated support channel for account-specific details. Remove tokens, API secrets, passwords, and credential-bearing URL components from attachments. A screenshot of the chart alone is usually insufficient because it doesn’t identify the delivery result, received payload, or broker response for the event under investigation.

Frequently asked questions

Start with the log, then fix the failed stage

When a TradingView webhook is not working, preserve the evidence before changing multiple settings. Identify the failed stage, correct that cause, and verify the result through the broker’s records. Follow the PickMyTrade alert setup guide for your connection when rebuilding the route.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: How to Test TradingView Automation Safely Before Going Live