How to fix alerts that got disabled on Kite
Kite auto-disables a price alert for a small set of defined reasons: a corporate action that moves the instrument’s price by more than 2 per cent, a derivative contract expiry, a delisting, suspension or series change, or the lapse of the alert’s 365-day validity. Separately, you cannot create a new alert once you hit the account cap of 500 alerts or 200 ATOs . A disabled alert no longer monitors anything, so a level you set and forgot can quietly stop watching. Kite emails you whenever an alert is disabled, which is the prompt to act.
This guide explains each disable reason, why the 2 per cent corporate-action rule exists, how to decide whether re-enabling still makes sense, the exact re-enable flow, and how to free slots when you have hit the limit. The fix is rarely just flipping the alert back on; after a corporate action the price level itself usually needs recomputing.
Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.
The disable reasons, and what each means
Kite turns an alert off automatically in these situations.
| Disable reason | What happened | What to do |
|---|---|---|
| Corporate action over 2 per cent | A dividend, bonus, split, or rights issue moved the price discontinuously | Recompute the level on the adjusted price, then re-enable or recreate |
| 365-day validity lapse | The alert reached the end of its one-year life without triggering | Re-enable or recreate if you still want the level watched |
| Derivative expiry | The futures or options contract the alert was on expired | Create a fresh alert on the live contract |
| Delisting, suspension, series change | The instrument changed or stopped trading | Re-evaluate; the old alert may no longer apply |
| Triggered | The alert fired and turned itself off | Recreate if you want to watch the condition again |
| Alert limit reached | You are at the 500-alert or 200-ATO cap | Delete stale alerts to free a slot, then create the new one |
The first four are the genuine auto-disables that surprise people. The last two, a fired alert and the cap, are not strictly “disabled” in the error sense but produce the same outcome: no monitoring, and in the cap case, no ability to create a new alert.
Why a corporate action over 2 per cent disables the alert
This is the disable reason worth understanding, because the fix is not just re-enabling. When a company does a bonus issue, a stock split, a rights issue, or pays an extraordinary dividend, the price adjusts discontinuously on the ex-date. A 1:1 bonus roughly halves the price; a 1:5 split quotes the stock at a fifth of its prior level; an extraordinary dividend drops the price by the dividend amount on the ex-date. Your alert level was set against the pre-action price. If it kept running, it would fire spuriously against the adjusted price, because a “below 250” alert on a stock that just split from 500 to 250 is now sitting on top of the price.
Kite’s rule is to disable any alert on an instrument whose price a corporate action moves by more than 2 per cent. The 2 per cent threshold separates an ordinary dividend (small, no adjustment needed) from an event that meaningfully resets the price. The disable is protective: it stops a stale level firing, and forces you to recompute the level against the adjusted price before the alert watches again. So the correct fix is to work out where your level sits on the new price, edit the alert to that level, and re-enable it, not to flip it back unchanged.
Step-by-step procedure
The infobox at the top gives the sequence. The detail below expands the diagnosis and the recompute step, which is where the real work is.
1. Read the disable email and open the Alerts section
Kite emails you when an alert is auto-disabled, so the email is your first signal. Open the Alerts section: Orders, then Alerts on web or app, or kite.zerodha.com/orders/alerts directly. Disabled alerts show in the list in a disabled state, distinct from your active ones.
2. Identify the disable reason
Match each disabled alert to its instrument’s recent history. Did the stock go ex-bonus, ex-split, ex-rights, or pay a large dividend in the last few sessions? Did the F&O contract expire? Was the scrip delisted, suspended, or moved to a new series? The reason determines whether re-enabling is even sensible: an alert on an expired contract has nothing to monitor, while a corporate-action alert needs its level recomputed first.
3. Re-check that the condition is still meaningful
For a corporate-action disable, the old level usually no longer means anything. An alert to buy “below 460” on a stock that did a 1:1 split now trades near 230 is pointing at a level the stock cleared on the ex-date. Recompute: if your thesis was “buy 8 per cent below the pre-split 500,” that is roughly 230 on the adjusted price, not 460. Do this arithmetic before you touch the enable toggle.
4. Re-enable the alert or recreate it
If the condition still holds unchanged, toggle the alert back to enabled in the Alerts section. If the level needs to change, edit the alert to the recomputed level, or delete it and recreate it with the adjusted condition. Either way the alert resumes monitoring once enabled with a valid level.
5. If you hit the alert limit, free slots
If Kite refuses a new alert outright, you are at the 500-alert or 200-ATO cap, not facing an auto-disable. Open the Alerts section and delete stale entries: triggered alerts that linger, expired-contract alerts, and alerts on instruments you no longer trade. Each deletion frees a slot. There is no bulk-clear, so work through them, then create the alert you wanted.
6. For an expired derivative, set the alert on the live contract
An alert on an expired future or option cannot usefully be re-enabled, because the contract no longer trades. Recreate the alert on the current contract instead: the new-month future, or the relevant live option. If you regularly alert on F&O, expect to refresh these alerts each expiry as contracts roll.
How you learn an alert was disabled
Kite sends an email notification whenever an alert is disabled. That email is the system’s only proactive signal, so the registered email on your account must be current and the message must not be filtered to spam. If you rely on alerts for risk management, treat a disable email as actionable, not informational: a disabled alert is a level you think is being watched but is not. The notification channels reference covers the email and push behaviour in full.
See also
- Kite alerts
- How to add and customise alerts on Kite
- How to modify or delete an alert on Kite
- Kite alert notifications
- How to fix a Kite alert that did not trigger
- Alert-Triggered Order (ATO) on Kite
- How to use Sentinel for cloud alerts
- Trigger price versus limit price
- GTT order on Zerodha
- How to place a GTT order on Kite
- Basket order on Kite
- Limit order on Kite
- Market order on Kite
- SL-M order on Kite
- Order validity types
- How to use the marketwatch on Kite
- Kite web reference
- Kite mobile app
- Kite by Zerodha
- Zerodha
- Zerodha Console
- National Stock Exchange
- Bombay Stock Exchange
- SEBI
External references
- Zerodha support: Why are Kite alerts disabled?
- Zerodha support: What are Kite alerts and how do I use them?
- Zerodha support: What is Alert Triggers Order (ATO)?
- Zerodha support: Alerts and nudges category
- Kite alerts page
References
- Zerodha support, Why are Kite alerts disabled? (corporate action over 2 per cent, derivative expiry, delisting or series change, 365-day validity, disable email; as of 21 June 2026).
- Zerodha support, What are Kite alerts and how do I use them? (500-alert and 200-ATO caps, 365-day validity; as of 21 June 2026).
- Zerodha support, What is Alert Triggers Order (ATO)? (corporate-action 2 per cent auto-disable on linked alerts; as of 21 June 2026).