Trading GTT Good Till Triggered Zerodha Kite order book day order

Why a triggered GTT is not visible after end of day on Kite

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~11 min.

Key facts

What a GTT becomes when it fires	A regular limit order at the exchange, with CNC Longterm product and Day validity for a delivery GTT
Why it vanishes after EOD	An unfilled day order is cancelled by the exchange at session close, so it does not appear from the next session onward
Trigger fires only once	A GTT trigger is valid once; after it fires the GTT is consumed and is not re-armed automatically
Where the executed record sits	In the Kite order book for the trigger day, and in the Console tradebook and order history thereafter
If it triggered but did not fill	There is no resting order to recover; you must place a fresh GTT or a fresh order

A triggered GTT is not visible after end of day on Kite because the trigger converts the GTT into a regular limit order with Day validity, and the exchange cancels any unfilled day order at session close. A GTT (Good Till Triggered) order on Zerodha is stored on Zerodha’s own servers, not at the exchange. The moment the last traded price meets the trigger condition, Zerodha’s server submits a normal limit order to the exchange, and from that instant the GTT stops being a persistent conditional order and starts being an ordinary order with the lifecycle of a single trading day.

That single distinction explains the whole problem traders report. The GTT was visible for months in the GTT tab; then it triggered, placed an order, and by the next morning both the GTT and its order were gone. Nothing failed silently. The order ran through its full lifecycle in one session and the exchange retired it at end of day, exactly as it retires every other unfilled day order. This article sets out what the triggered order actually is, why it disappears, where the record still lives, and how to recover the position you intended.

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.

What the trigger actually does to the GTT

A GTT is a two-part instruction. The trigger decides when, the limit price decides the worst fill price. While the GTT waits, Zerodha’s engine watches the last traded price during market hours and the order sits nowhere on the exchange. When the trigger condition is met, Zerodha places a regular limit order to the exchange on your behalf.

The order it places carries a specific product and validity. For an equity delivery GTT the resulting order is a CNC (cash and carry ) order with Longterm tagging and Day validity. Zerodha’s own description is direct: once triggered, the order “remains valid for the remainder of the trading day as a CNC (Longterm) limit order with Day validity.” This is the same Day validity that governs a normal limit order you type into the order window in the morning. It is alive for one session and no longer.

The trigger itself is consumed in the act of firing. A GTT trigger is valid only once. After it fires, the GTT is finished, whether the resulting order filled, partially filled, or lapsed without filling. It is not re-armed for the next day. So the GTT you placed and the GTT you see the next morning are not the same thing: the original GTT no longer exists as a pending instruction once its trigger has fired.

Why the order is gone the next session

The disappearance has two stages, and most traders conflate them.

First, the GTT leaves the GTT tab the moment it triggers, because the trigger is spent. A fired GTT is not a pending GTT, so it stops appearing in the list of active GTTs. That is expected behaviour, not a glitch.

Second, the order that the trigger placed runs through the ordinary day-order lifecycle. If the limit order fills during the session, you hold the position and a trade record exists. If it does not fill, the exchange treats it like any other unfilled day order: “At the end of the day, the exchange treats it like any other normal day order and cancels it.” Zerodha states the consequence plainly: “your order is not visible from the next day onwards.” There is no resting order at the exchange after EOD cancellation, because a Day order does not carry into the next session by design.

So a GTT that triggered late in the session, placed a limit order above the prevailing market for a buy or below it for a sell, and never filled, will show nothing the next morning. The GTT is spent, and the day order it created has been cancelled overnight by the exchange. Both halves of what you placed are gone, and neither will resurrect itself.

Triggered and executed versus triggered and not executed

The visibility question depends entirely on whether the triggered order filled. The two outcomes diverge sharply.

A GTT that triggered and executed leaves a trade. The shares are credited (on T+1 settlement for a CNC buy), the position appears in holdings or positions, and the trade is recorded permanently in the tradebook. Nothing is lost; the order simply matured into a completed trade and is no longer a live order because it is done.

A GTT that triggered but did not execute leaves no trade and, after EOD, no order. The classic cause is a price mismatch: the order’s limit price did not match the available price in the market. A sell GTT with trigger Rs 88 and limit Rs 87 can fire on a gap-down and find the stock already trading at Rs 80, leaving a sell limit at Rs 87 with no buyer at that price. The limit rests unfilled through the session, the exchange cancels it at close, and the next morning there is nothing to see. For the mechanics of that gap-and-miss case, see why a GTT triggered but did not execute .

This is the structural reason a GTT is a weaker stop than an SL-M order . An SL-M converts to a market order and fills at whatever price the book offers. A GTT always places a limit order, which can be left stranded by a fast move, and the stranded limit is then cancelled at EOD without any retry.

Where the record still lives

The day order is gone after EOD, but the record of what happened is not. Three surfaces hold it, with different retention.

Surface	What it shows	Retention after EOD
Kite order book	The triggered order, marked executed, cancelled, or rejected	Same trading day only; cleared overnight
Kite GTT tab	Active and recently triggered GTTs, with the triggered state	Triggered GTTs drop out as the list refreshes; not a permanent ledger
Zerodha Console	Order history and tradebook	Permanent; the canonical record of fills and order events

The practical rule: for anything beyond the trigger day, go to Console , not Kite. Console’s order history retains the order events and the tradebook retains the fills regardless of the overnight day-order cleanup on Kite. The Kite order book is a live view of the current session and is not the place to audit what a GTT did last week. To locate the GTT itself and its current state while it is still on Kite, use the GTT tab as set out in how to find your GTT orders on Kite .

The notification trail you should have received

You are not meant to learn about a trigger by noticing a missing GTT the next day. Zerodha notifies on the trigger event itself: “You receive a notification on your registered email and mobile device every time your GTT triggers and an order is placed on the exchange.” Separately, if the resulting order is rejected, Zerodha “sends you both a push notification and an email whenever a GTT order gets rejected.”

So the sequence that leaves you with nothing the next day should have produced two signals on the trigger day: a trigger notification when the GTT fired and placed the order, and, if the order was rejected outright, a rejection notification with the reason. A triggered-but-unfilled order that simply lapsed at EOD does not generate a rejection notice, because it was not rejected; it was a valid order that found no counterparty and then expired with the session. For the full sequence from trigger to fill, see the GTT notification flow .

What to do when a triggered GTT left you with nothing

There is no resting order to recover and no GTT to re-arm. The recovery is a fresh instruction, and the right one depends on what you were trying to do.

If the GTT was a buy target that triggered but did not fill because the price ran away, decide whether you still want the stock at the new level. If yes, place a fresh order or a fresh GTT at a realistic level; do not assume the old GTT will fire again, because it will not.

If the GTT was a stop-loss that triggered but did not fill, your position is still open and unprotected, which is the dangerous case. Replace the protection immediately, and consider whether a GTT was the right tool: a GTT places a limit order that can be skipped on a gap, where an SL-M would have exited at market. For a position you must protect against gaps, a GTT alone is not sufficient.

If you simply could not find the GTT and assumed it was deleted, confirm its real state first. A GTT that vanished may have triggered, or it may have been auto-disabled by a corporate action, which is a different problem with a different fix; see GTT states: active, triggered, cancelled, expired, deleted, and disabled .

External references

References

Zerodha support, Why is my triggered GTT order pending execution not visible? (as of 21 June 2026).
Zerodha support, Why was my GTT order triggered but not executed? (as of 21 June 2026).
Zerodha support, What is the Good Till Triggered (GTT) feature and its types? (as of 21 June 2026).
Zerodha terms of service for GTT orders, zerodha.com/tos/gtt (as of 21 June 2026).

Frequently asked questions

Why has my triggered GTT disappeared the next day on Kite?

When a GTT triggers it places a regular limit order with Day validity. If that order does not fill, the exchange cancels it at end of day like any normal day order, so it is not visible from the next session onward. The GTT trigger fires only once.

Where do I find a GTT that triggered but did not execute?

On the trigger day it sits in the Kite order book as a cancelled or rejected order. From the next day, check Zerodha Console: the order history and tradebook keep the record permanently even though Kite clears the day order overnight.

Does a GTT come back if its order is cancelled at end of day?

No. A GTT trigger is valid only once. Once it fires, the GTT is consumed whether or not the resulting order filled. If the order lapsed unfilled at EOD, you must create a fresh GTT or place a fresh order yourself.

Is a triggered GTT the same as a resting order at the exchange?

Only after it triggers. Before the trigger, the GTT sits on Zerodha’s servers, not at the exchange. When the last traded price meets the trigger, Zerodha submits a limit Day order to the exchange, and from that point it is a normal exchange order subject to the day-order lifecycle.

Why does my GTT show triggered but I never got the shares?

A trigger places a limit order, not a market order. If the price moved past your limit before the order filled, the limit rests unfilled and the exchange cancels it at end of day. The GTT is still marked triggered, but no trade happened, so no shares were credited.

Can I see GTT history on Kite after the day it triggered?

Kite shows live and same-day orders. For history beyond the trigger day, use the GTT tab for active and recent GTTs and Zerodha Console for the permanent order and trade record, since the day order itself is gone after EOD cancellation.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.