Your effective alert ceiling depends on your subscription tier and how you split alerts between Price and Technical categories, which typically doubles your real capacity compared to the raw plan number. Start by checking your Alert Manager counters right now, convert simple technical triggers into price alerts where you can, and add {{timenow}} to your messages before you assume anything is broken. Most “delayed” alerts aren’t delayed at all. They’re just misread against candle timing.
TL;DR:
Technical alerts often consume more quota than price alerts, so converting static indicator levels into simple price triggers can free up valuable alert capacity.
Hitting the 15-times-in-three-minutes throttle limit requires redesigning alert logic to avoid excessive firing, especially for high-frequency or scalping strategies.
Regularly monitoring your Alert Manager counters and activity logs helps prevent unexpected alert stoppages caused by quota exhaustion or throttling.
Consolidating similar alerts into webhooks or routing signals through automation platforms can extend your effective alert capacity without plan upgrades.
Delays perceived in alert triggering are usually due to candle timing settings and can be diagnosed by adding timestamp tags and checking alert activity logs.
Table of Contents
What Are TradingView’s Alert Limits by Plan?
TradingView splits your alert budget into separate buckets for Price, Technical, and Watchlist alerts, and each subscription tier gets its own ceiling for each. This split matters more than most traders realize. Because Price and Technical alerts draw from different pools, a trader who hits their technical cap can often keep running dozens more alerts simply by shifting logic into simple price triggers.
According to TradingView’s pricing page, limits scale up meaningfully as you move up tiers, with Premium and Ultimate offering the highest per-category ceilings. Rough tier breakdown:
-
Basic (free): A small number of total alerts, with Technical alerts especially limited.
-
Pro: A modest bump in both Price and Technical quotas, still limited for active multi-symbol strategies.
-
Pro+: Meaningfully higher totals, workable for traders running a handful of strategies.
-
Premium: Documented examples show around 400 price alerts plus 400 technical alerts.
-
Ultimate: The highest ceiling, with examples around 1,000 price and 1,000 technical alerts.
TradingView rolled out this split-limit structure specifically to stretch usable capacity without forcing a blanket increase across the board. Your exact numbers live in Alert Manager, not in any generic chart. Check it before you plan your alert architecture, since limits do shift between plan revisions.
What Counts as a Price Alert vs. a Technical Alert?
Category classification decides which quota bucket your alert draws from, and getting this wrong is the fastest way to burn through your technical allowance for no reason.
A Price alert only needs a symbol and a price operator: Crossing, Greater Than, Less Than, and similar comparisons. A Technical alert covers anything built on indicators, drawings, or strategies, according to TradingView’s own alert-type documentation. That distinction determines which pool gets debited.
In Pine Script, each alertcondition() call counts against your quota and adds to your script’s plot count, while alert() behaves differently and sidesteps some of those plot-count constraints, per the Pine Script alerts FAQ.
-
Price alert: “Alert when BTCUSD crosses $65,000.”
-
Technical alert: “Alert when RSI crosses above 70 on a custom indicator.”
If your indicator plots a fixed level, you can often read that value off the chart and set a plain Crossing price alert instead of burning a technical slot.
Pro Tip: Before building a technical alert around a static indicator value, check whether the trigger price is stable enough to hardcode into a simple price alert instead. You keep the same signal and pay a fraction of the quota cost.
Why Do TradingView Alerts Look Delayed?
Most perceived delays are a timing illusion, not a transmission problem. An alert set to fire “Once Per Bar Close” won’t trigger until the candle actually closes, even though the underlying condition was true minutes earlier inside the bar. That gap feels like lag. It isn’t.
-
Check whether your alert is set to Once Per Bar or Once Per Bar Close. The latter always waits for candle close by design.
-
Add
{{timenow}}to your alert message. Comparing that timestamp against when you received the notification isolates real transmission time from candle timing, a diagnostic step documented in detail here. -
Open Tools → Activity or your Alert Trail to see when the alert actually fired versus when your endpoint received it.
-
If TradingView’s fire time and your received timeline up, the lag is happening downstream, in your broker or execution pipeline, not on TradingView’s end. That’s where reducing round-trip latency becomes relevant.
Run this sequence before you touch any code. It takes minutes and usually settles the question outright.
How Do You Free Up or Increase Usable Alerts?
You don’t need to upgrade the moment you hit a wall. Several tactics recover slots without spending a dollar.
-
Convert technical triggers to price alerts. Read the indicator’s current trigger value and set a Crossing or Greater Than alert on that value directly, a swap TradingView itself recommends for preserving technical quota.
-
Consolidate similar triggers into one webhook alert. Instead of five near-identical alerts across correlated pairs, send one alert with a parsed payload and let your automation layer route the logic downstream.
-
Add debounce and filter logic. Require a minimum price move or a minimum time gap between triggers on the same symbol, so a choppy market doesn’t burn through your frequency allowance.
Pro Tip: Before consolidating alerts into a single webhook, sketch out your payload structure first. A messy multi-symbol webhook that isn’t parsed cleanly downstream causes more debugging headaches than the quota problem it was meant to solve.
What Happens When You Hit TradingView’s Rate Limits?
TradingView enforces hard frequency throttles separate from your plan quota. If an alert fires more than 15 times within a three-minute window, TradingView stops that alert from firing further until you re-enable it manually. Watchlist alerts carry their own aggregate trigger caps, which matters if you’re monitoring a large watchlist of correlated symbols that can all spike at once.
-
Design alerts so no single symbol can realistically fire 15 times in three minutes; that usually means a scalping or tick-based strategy needs offline aggregation instead.
-
Spread high-frequency logic across multiple narrower alerts rather than one alert monitoring dozens of symbols.
-
Treat a stopped alert as a design signal, not a bug. It’s telling you the trigger condition is too loose.
How Do You Monitor Your Alert Usage on TradingView?
Alert health is only visible if you actually look. Building a habit around three checkpoints keeps you from getting blindsided by a stopped alert mid session.
-
Open Alert Manager and read your Price (P) and Technical (T) counters against your plan ceiling. This tells you exactly how much headroom remains in each bucket.
-
Use Alert Trail and Tools → Activity to compare
timenowtimestamps against received times, catching latency or throttle issues before they cost you a trade. -
Adopt a naming convention (symbol, type, condition) so alerts are identifiable at a glance instead of a wall of generic labels.
-
Keep a simple inventory, even a basic spreadsheet tracking symbol, type, trigger condition, and webhook endpoint, so pruning stale alerts is safe and repeatable rather than guesswork.
When Is It Time to Stop Optimizing and Automate?
Squeezing more mileage out of your alert quota has a ceiling, and that ceiling shows up fast once you’re running more than a handful of strategies. Optimization tactics buy you time. They don’t solve the deeper problem: every added alert is another point of manual friction between a signal and an executed trade, and broker latency on the receiving end can quietly erode whatever speed you gained upstream.
For traders running one or two strategies, converting technical alerts to price alerts and tightening frequency filters is probably enough. For anyone juggling multiple strategies across several symbols or asset classes, routing alerts through an automation platform stops being a convenience and becomes the more reliable architecture.— Jay
How Tickerly Turns Alert Limits Into a Non-Issue
Instead of stretching your quota with workarounds, you route your strategy signals into Tickerly and it executes them as fully automated trades, connecting directly to your exchange with minimal manual handling.
That matters most once you’re running multiple strategies at once. Rather than juggling separate alerts for every symbol and condition, Tickerly consolidates execution so alert-count math stops being your bottleneck. It supports multiple asset classes, connects to exchange APIs for order placement, and can handle multiple strategies running concurrently.
If you’re hitting alert ceilings or find webhook payloads hard to manage, that’s the signal to consider automating past those limits. Read the TradingView strategy automation guide to see exactly how alerts map to live orders, and start your trial today.
FAQ
How Can I Get More Alerts on TradingView for Free?
Convert technical alerts (indicators, drawings, strategies) into simple price alerts wherever the trigger value is stable, since Price and Technical alerts draw from separate quota buckets. Consolidating correlated symbols into one webhook alert also frees up slots without any plan change.
What Is the Alert Limit on TradingView?
Limits vary by plan and category: Basic and Pro tiers get modest Price and Technical allowances, while Premium offers around 400 of each and Ultimate reaches roughly 1,000 of each. Check Alert Manager for your account’s exact current numbers.
Why Are My TradingView Alerts Not Triggering?
Most “not triggering” complaints often result from candle timing: an alert set to Once Per Bar Close waits until the bar closes before firing, which can feel like a delay or a failure. Add {{timenow}} to your alert message and check Alert Trail to confirm whether the alert actually fired on time.
What Happens If I Exceed TradingView’s Alert Frequency Limit?
If an alert triggers more than 15 times within three minutes, TradingView halts that alert until you manually reactivate it. Watchlist alerts carry a similar aggregate cap across the symbols being monitored.
Should I Upgrade My Plan or Automate My Alerts Instead?
Upgrade if you’re running genuinely distinct strategies and simply need more slots. If one strategy is firing repeatedly across many symbols, routing signals through an automation platform like Tickerly usually solves the underlying volume problem better than a higher tier does.
Recommended
This article was produced with Al assistance and reviewed for accuracy. It is provided for general information only and is not professional or financial advice.