The GTT notification flow on Zerodha
The GTT notification flow on Zerodha has two guaranteed alerts: an email and a mobile notification when a GTT triggers and places an order, and a push notification plus email if that order is rejected. A GTT (Good Till Triggered) order on Zerodha sits dormant on Zerodha’s servers, sometimes for months, so the notification is the only signal that it has acted. Zerodha’s own wording is direct: “You receive a notification on your registered email and mobile device every time your GTT triggers and an order is placed on the exchange,” and it “sends you both a push notification and an email whenever a GTT order gets rejected.”
The flow matters because the alerts mark events, not outcomes. A trigger notification confirms the GTT fired and an order went to the exchange; it does not confirm the order filled. A rejection notification confirms the exchange refused the order; it does not cover the quieter case of an order that was accepted but never matched and then lapsed at end of day. Reading the notifications correctly is the difference between knowing your stop executed and assuming it did when the limit was skipped. This article sets out the full sequence from trigger to placement to fill, names what each notification does and does not tell you, and shows where to confirm the parts the alerts leave out.
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 sequence, event by event
A GTT moves through a fixed sequence once the market reaches its trigger. Each stage either produces a notification or leaves a record you must check yourself.
| Stage | What happens | Notification |
|---|---|---|
| Dormant | GTT waits on Zerodha’s servers; engine watches the last traded price in market hours | None |
| Trigger | Last traded price meets the trigger condition; Zerodha submits a limit order to the exchange | Email and mobile-device notification |
| Acceptance or rejection | The exchange accepts the order, or rejects it (insufficient holdings, price band, and similar) | Push notification and email on rejection |
| Fill or lapse | The accepted limit order matches and fills, or rests unfilled and is cancelled at EOD | Order-book and tradebook record; no separate rejection alert on a lapse |
The two notification events are the trigger and the rejection. The fill is not a separate alert in this flow; it is recorded in the order book and tradebook as an order event. So the presence of a trigger notification with no rejection notification does not by itself prove a fill. It proves the GTT fired and the order was placed and not rejected. Whether it filled is a question for the order book.
The trigger notification: what it confirms
When the last traded price meets the trigger during market hours, Zerodha’s server places a regular limit order to the exchange and notifies you on email and your registered mobile device. The mobile alert is delivered through the Kite app notification on the registered device, so app notifications must be enabled for it to reach you.
The trigger notification confirms two things: the GTT condition was met, and an order was placed on the exchange. The order it placed is a normal limit order. For an equity delivery GTT it is a CNC Longterm order with Day validity; for the mechanics of what that order becomes, see why a triggered GTT is not visible after end of day . What the trigger notification does not confirm is a fill. A limit order can be placed and still miss, which is why the next stage exists.
The rejection notification: when the exchange refuses
If the order the trigger placed is rejected, Zerodha sends both a push notification and an email, and the message carries the reason. Rejection is distinct from non-fill: a rejected order never rested in the book at all, because the exchange or Zerodha’s risk system refused it on submission.
Common rejection reasons on a triggered GTT order include insufficient holdings on a sell GTT, a missing CDSL TPIN authorisation on a non-DDPI account, a limit price outside the day’s circuit band, and the instrument having no buyers or sellers at the limit. For a sell GTT specifically, the rejection often traces to holdings or authorisation; see how to fix a rejected sell GTT and why a buy GTT was rejected . The rejection notification is your cue to act on the same trading day, because the GTT trigger is spent and will not retry.
The fill: an event the flow does not separately alert
The gap most traders miss sits between acceptance and fill. An accepted limit order is not a completed trade. If the price has moved past your limit, the order rests unfilled, finds no counterparty, and is cancelled by the exchange at end of day along with every other unfilled day order. This produces no rejection notification, because the order was not rejected; it was valid and simply unmatched.
So a GTT can leave you with a trigger notification, no rejection notification, and no shares. That is the quietest failure in the flow and the one that catches stop-loss users. Zerodha advises setting the limit beyond the trigger, a buy limit above the trigger and a sell limit below it, so a fast market still fills. For the full mechanics of the triggered-but-unfilled case, see why a GTT triggered but did not execute . The way to confirm a fill is not the notification log; it is the order book and tradebook.
Where to confirm what the notifications leave out
Because the fill is not separately notified, treat the notifications as prompts to verify, not as a complete ledger.
- For the live state of the order on the trigger day, open the Kite order book . A filled order shows as complete; an unfilled one shows as cancelled or rejected at EOD.
- For the permanent record beyond the trigger day, use Zerodha Console . The order history retains the order events and the tradebook retains the fills, regardless of the overnight day-order cleanup on Kite.
- For the GTT itself and its current state, use the GTT tab as set out in how to find your GTT orders on Kite .
The discipline is simple: a trigger notification means check the order book; a rejection notification means read the reason and replace the GTT; no notification at all on a GTT you expected to fire means check whether it is still active or was disabled, per how to diagnose why a GTT did not trigger .
Keeping the notification channels reliable
The flow only works if both channels reach you. Two practical points govern reliability.
Keep your registered email and registered mobile current with Zerodha, because the notifications go to the registered details, not to any address you happen to be logged in on. And keep the Kite app installed with notifications enabled on the registered device, since the mobile trigger alert is delivered as a Kite app notification. A trader who relies on a GTT as a stop but has app notifications muted has disabled half the notification flow and will learn of a trigger only by checking the GTT tab.
For broader control over what Kite alerts you about, including price alerts that are separate from GTT triggers, see Kite alerts and how to add and customise alerts on Kite . A price alert and a GTT trigger are different mechanisms: an alert notifies and does nothing, a GTT notifies and places an order.
See also
- GTT (Good Till Triggered) order on Zerodha
- How to place a GTT order on Kite
- How to find your GTT orders on Kite
- Why a triggered GTT is not visible after end of day
- Why a GTT triggered but did not execute
- How to diagnose why a GTT did not trigger
- GTT states: active, triggered, cancelled, expired, deleted, and disabled
- GTT validity rules on Kite
- How to fix a rejected sell GTT
- Why was a buy GTT rejected
- GTT order limitations and rejection
- How to modify a GTT on Kite
- How to delete a GTT on Kite
- Kite alerts
- How to add and customise alerts on Kite
- CNC product code
- SL-M order on Kite
- Limit order on Kite
- Trigger price versus limit price
- Order validity types
- Zerodha Console
- Kite by Zerodha
- Zerodha
- National Stock Exchange
- Bombay Stock Exchange
External references
- Zerodha support: What is the Good Till Triggered (GTT) feature and its types?
- Zerodha support: Why are GTTs disabled, cancelled, expired, or rejected?
- Zerodha support: Why was my GTT order triggered but not executed?
- Zerodha support: How can I use the GTT feature?
- Zerodha GTT product page
References
- Zerodha support, What is the Good Till Triggered (GTT) feature and its types? (as of 21 June 2026).
- Zerodha support, Why are GTTs disabled, cancelled, expired, or rejected? (as of 21 June 2026).
- Zerodha support, Why was my GTT order triggered but not executed? (as of 21 June 2026).
- Zerodha support, How can I use the GTT feature? (as of 21 June 2026).