TradingView alerts not working today — Quick Fixes

If you searched for tradingview alerts not working today, this article gives a comprehensive, step-by-step troubleshooting guide, practical fixes, and preventative measures to get your alerts firing reliably. You’ll learn how to isolate whether the problem is a TradingView outage, account limits, Pine Script or alert configuration mistakes, webhook/server problems, or device notification settings. The guide also suggests robust alert architectures and links to useful resources and exchanges if you want to automate trades after your alerts trigger.

Quick checklist — fast ways to diagnose the problem

• Check TradingView status: Visit the official status page to confirm platform-wide outages or degraded services.
• Test a simple price alert: Create an alert on a major ticker (e.g., BTCUSD) crossing a price level to verify core alerting works.
• Confirm plan limits: Ensure you haven’t hit the active-alert limit for your subscription tier.
• Verify notification channels: Mobile push, email, webhook, and browser notifications may have different problems — test each one independently.
• Review alert logs and messages: Double-check your alert message content and template placeholders if using Pine Script.
• Check mobile/OS settings: Ensure TradingView notifications are enabled in your device settings and not blocked by Do Not Disturb or battery optimization.

Why TradingView alerts fail (common root causes)

Alerts can fail for many reasons. Categorizing the causes helps you find a quicker fix:

• Platform/Server Issues: TradingView could be partially or fully down, or alert delivery servers could be delayed.
• Account/Subscription Limits: Free and paid tiers have limits on active alerts and webhook usage.
• Alert Configuration or Pine Script Errors: Incorrect use of alertcondition(), alert(), or creating the alert from the wrong panel.
• Notification Channel Problems: Email going to spam, mobile push blocked by OS, browser notifications disabled, or webhook endpoint misconfigured.
• Network, Firewall, or SSL Issues: Webhook endpoints with invalid certificates or blocked ports will cause failed deliveries.
• Third-party Relay Failures: Services like Zapier, Alertatron, or a Telegram bot may be down or misconfigured.
• Human Errors: Wrong symbol/timeframe selected, alert set to a condition that never occurs, or alert set to “Only once” and already triggered.

Step-by-step troubleshooting (start here)

1. Confirm TradingView’s status

Before changing anything, check if TradingView is experiencing an outage. Visit the official TradingView status page to see live incident reports and maintenance notices. You can also check the TradingView Wikipedia entry for background, and community sites like Reddit for reports from other users.

• TradingView status: status.tradingview.com
• TradingView on Wikipedia: TradingView — Wikipedia

2. Test a simple, guaranteed alert

Create a basic alert to isolate whether alerts are working at the platform level:

1. Open BTCUSD (or another liquid instrument).
2. Right-click the chart price and choose “Add alert” (or click the alert icon).
3. Set condition like “Price crosses 1” (a level very far away or just use a small price offset depending on market). Set it to trigger “Once per bar close” or “Once per bar” for quick tests.
4. Enable at least one delivery channel — mobile push and email are usually quickest to test.

If this alert fires, the TradingView engine is working and the problem is likely with your specific custom alerts, Pine Script code, or webhook destination.

3. Check your subscription and alert limits

Active alert limits are tied to your TradingView plan. If you have reached the maximum number of active alerts, new alerts will not be created or triggered. To resolve:

• Open your account settings and verify the number of active alerts.
• Close or delete old alerts you no longer need.
• Consider upgrading your plan if you require many concurrent alerts.
• Link: TradingView plans and limits — check the “Go Pro” page on TradingView for up-to-date details.

4. Inspect alert notification channel settings

Different channels can fail independently. Test each:

• Mobile push: Ensure you’re logged into the TradingView mobile app with the same account that created the alert. Check OS-level notification permissions, DND modes, and background app restrictions (Android battery savers).
• Email: Confirm your email address in TradingView profile and check spam/junk folders. Some mail providers block automated messages or delay them.
• Browser push: Make sure browser notifications are allowed for TradingView and that you are logged in. Some browsers require that a tab with TradingView be active or open for web socket connection persistence.
• Webhook: Confirm the endpoint URL, ensure it accepts POST requests with JSON, uses a valid SSL certificate, and is reachable from the internet.

5. Validate Pine Script alerts and indicator usage

If you use Pine Script indicators or strategies, some common mistakes prevent alerts from firing:

• Use alertcondition() to define named conditions and then create alerts using the indicator (not the strategy) if needed. If you use alert() inside the script, understand it triggers only when the script runs and conditions are met.
• Create the alert from the indicator’s “Create Alert” button (three-dot menu) rather than the chart’s generic alert dialog if you want the indicator’s logic.
• Check whether your script’s conditions execute on each bar or only on bar close; using “Once Per Bar Close” can delay or prevent firing if you expect intra-bar triggers.
• Use clear, testable alert messages that include placeholders like {{ticker}} or {{close}} so you can debug message content.

Refer to TradingView’s Pine Script docs for syntax and best practices: Pine Script documentation.

6. Webhook troubleshooting — common problems and fixes

Webhooks are a powerful way to automate trade execution, but they are also a common point of failure:

• HTTPS required: Your endpoint must use HTTPS with a valid CA-signed SSL certificate. Self-signed certs will be rejected.
• Return codes: TradingView expects a 200-series HTTP response. A 4xx or 5xx error means your server rejected the request; check server logs for details.
• Firewall and IP restrictions: If your webhook receiver restricts source IPs, ensure TradingView’s outgoing IPs are allowed or use a publicly available relay like Zapier or a webhook relay service.
• Payload format: TradingView sends the exact message you enter in the alert. If your endpoint expects a different JSON structure, convert or map the fields accordingly.
• Testing: Use curl or Postman to simulate TradingView POST requests and verify your endpoint works before relying on alerts for live execution.

Example: Fixing a webhook that returns 403

1. Check server logs to see why requests are rejected — look for authentication middleware failing or IP blocking rules.
2. Verify the webhook URL uses HTTPS and is publicly reachable (no VPN or internal-only hostnames).
3. If you use a bot token (e.g., Telegram), ensure the token is valid and placed correctly in the alert message.
4. Test with a simple POST using curl: curl -X POST -H "Content-Type: application/json" -d '{"test":"1"}' https://your-endpoint.example/test

Mobile notification issues (Android / iOS)

• Ensure the TradingView mobile app is logged into the same account and notifications are enabled in Settings → Notifications.
• On Android, disable battery optimization for TradingView to prevent the OS from killing background services.
• On iOS, allow background app refresh and notification permissions. DND or Focus modes may suppress notifications.
• Reinstalling the app or logging out and back in sometimes re-registers device tokens on TradingView’s servers.

Email issues

• Check the email address listed in your TradingView account; confirm you verified it.
• Search in spam/junk folders and set a filter to always allow messages from TradingView.
• Try using a different email provider temporarily — some providers throttle or block automated emails.

Advanced: Building a robust alert architecture (recommended for automation)

If you’re automating trades or using alerts for high-value signals, consider these design elements:

• Redundancy: Send alerts to multiple channels (webhook + mobile + email) so a single channel failure won’t cause a missed trade.
• Intermediate relay: Use a reliable, monitored intermediary (e.g., an AWS Lambda function, Heroku app, or a service like Zapier/Make) that receives TradingView webhooks and forwards them to the final execution engine (exchange API, Telegram bot, etc.).
• Idempotency and deduplication: Include unique IDs or timestamps in alert messages so your execution system ignores duplicate webhooks.
• Logging and retries: Keep logs and implement retry logic for transient HTTP failures.
• Security: Use HMAC or token-based validation in webhook messages to prevent unauthorized submissions.
• Monitoring: Build a simple dashboard or alert-on-alerts that notifies you if no alerts have been received for a defined period.

Testing methodology (how to confirm you’ve fixed the issue)

1. Create a controlled alert with a guaranteed trigger (e.g., set a price threshold you can manually push the market to or use a volatile instrument).
2. Enable multiple notification channels for the same alert (email + webhook + mobile).
3. Trigger the condition and verify delivery to all channels. Check server logs for webhook HTTP status and body content.
4. If using a Pine Script, add debug prints to the alert message (like bar index or timestamp) to ensure the condition fired when expected.

Common user mistakes and how to avoid them

• Creating the alert on the wrong timeframe or wrong symbol — double-check the chart you’re using.
• Setting alerts to trigger “Only once” and forgetting they already fired — set appropriate repetition logic.
• Using dynamic price inputs in the message that confuse your webhook parser — stick to a JSON structure or fixed template.
• Relying on a single notification channel — always have at least one backup.

Useful third-party services and integrations

If TradingView alerts are mission-critical, consider integrating with third-party automation/relay services that specialize in handling alerts and executing trades:

• Zapier / Make (Integromat) — good for simple workflows and relays.
• Alertatron, 3Commas — platforms designed specifically for executing crypto signals from alerts.
• Self-hosted relay (AWS Lambda, Google Cloud Functions) — gives you complete control and reliability at scale.

Resources and reading (including smart trading guides)

For advanced smart trading workflows and combining TradingView alerts with execution strategies, these guides are helpful:

• Bitcoin signals & smart trading alerts guide — a practical resource for integrating signals with automated trading systems.
• Crypto IDX Binomo signal live Telegram guide (2025) — an example of linking TradingView alerts to live Telegram signal channels.
• Futu trading fee explained (2025) — useful when deciding which exchange to route automated trades to based on fees.
• Pine Script docs: Official Pine Script documentation
• TradingView status: Official status page
• Webhooks overview: Webhook — Wikipedia

When to contact TradingView support

If you’ve verified it’s not an account limit, not a problem with your webhook or device, and TradingView status shows normal operation, open a support ticket. Provide these details to accelerate resolution:

• Account email and username
• Exact alert ID or a screenshot of the alert configuration
• Timestamp(s) where alerts should have fired and the market data snapshot
• Webhook endpoint URL (or sample), expected payload, and server response codes
• Any recent changes to your Pine Script or indicator

Examples of real-world troubleshooting scenarios

Scenario A — Alerts fired but no webhook actions executed

Root cause: Webhook endpoint rejected the request with 401/403 because the token format changed.

Fix: Update token format in TradingView alert, test with curl, implement a server-side log that prints incoming request bodies and headers.

Scenario B — Mobile push not received but email arrived

Root cause: App was logged out or device token expired; Android battery optimization was blocking background processes.

Fix: Log back into the TradingView app, disable battery optimizations for TradingView, and re-register notifications by restarting the app.

Scenario C — Pine Script conditions not detected

Root cause: The alert was created using the chart’s alert dialog instead of the indicator-specific alert; the indicator uses alertcondition() but no alert was linked to it.

Fix: Use the indicator’s menu to create the alert and choose the correct alertcondition from the list.

Prevention: Best practices to avoid "tradingview alerts not working today" tomorrow

• Keep a small number of active alerts and retire ones you don’t need.
• Use multi-channel notifications for redundancy (webhook + push + email).
• Design alert payloads for idempotency (include a unique alert ID/timestamp).
• Monitor TradingView status and set an “alert-on-alerts” if you rely on alerts for live trading.
• Document your workflows and have a test alert routine to run weekly.

Where to execute trades after alerts (recommended exchanges)

If your alerts are for crypto trades and you want to automate execution, you’ll need accounts on exchanges that provide APIs and good reliability. Here are commonly used exchanges (referral links included):

• Register on Binance — widely used, extensive API functionality.
• Open a MEXC account — emerging platform with many altcoins.
• Create a Bitget account — popular for derivatives and copy trading.
• Join Bybit — strong derivatives and API support.

Consider fee structures, API rate limits, and order types when choosing an exchange. The previously linked Futu trading fee article can help with fee comparisons and deciding where to route trades.

Final checklist before you go live with alerts

1. Verify a simple test alert on the real instrument and ensure delivery to all channels.
2. Confirm your webhook endpoint returns HTTP 200 and logs the request body.
3. Check Pine Script alertconditions and use clear, testable messages.
4. Monitor alert counts against your TradingView subscription and plan for expansion if you scale up.
5. Deploy redundancy: multiple channels, a relay with retries, and alert logging.

Conclusion

When tradingview alerts not working today, follow a methodical approach: check TradingView’s status, test simple alerts, verify account limits, inspect notification channels, and troubleshoot webhooks or Pine Script logic. Building a resilient alert system with redundancy and logging prevents missed signals from becoming missed opportunities. Use the offered resources for smart trading alerts and integrate with reliable exchanges if you plan to automate execution. If you still can’t resolve the issue after these steps, collect detailed logs and contact TradingView support for assistance.

Further reading and resources to help you implement robust alerts and automation:

• Bitcoin signals & smart trading alerts guide
• Crypto IDX Binomo signal live Telegram guide (2025)
• Futu trading fee explained (2025)