LTP on WebNotes

How to fix a Kite alert that did not trigger

Sun, 21 Jun 2026 00:00:00 +0000

A Kite alert evaluates on the recorded last traded price, and the most common reason one does not fire even though the price appeared to hit your level is a missed tick: the LTP momentarily reached the level, but that tick was not captured, so the alert stayed pending. Before you conclude that, though, three cheaper explanations need ruling out: the alert was disabled and never monitoring, the alert was on a different exchange than the price you watched, or no trade actually printed at your level. This guide works through them in the order worth checking, from most common and easiest to confirm to the genuine missed-tick case that only Zerodha can investigate.

Why limit orders placed far from the LTP are rejected on Kite

Sun, 21 Jun 2026 00:00:00 +0000

A limit order rejected for being far from the LTP is a freak-trade safeguard: Zerodha blocks limit orders in stock and index options placed 50% to 150% away from the last traded price, and the exchange separately cancels orders outside a dynamic Price Reasonability Range , because an order priced far from the current market can execute at a level unrelated to fair value and distort price discovery. The fix is to price the order closer to the LTP, or to use a GTT order , which is exempt from the far-from-LTP block.

F&O LTP change on Positions before market opens on Kite

Wed, 20 May 2026 00:00:00 +0000

Open F&O positions held overnight on Kite can show LTP changes (and consequently MTM P&L changes) before the next trading session opens at 09:15. This is not a bug; several settlement and pre-market mechanisms can move the displayed LTP outside session hours.

Why LTP changes overnight

1. Settlement price replaces LTP at end of T

For each F&O contract, the exchange computes a daily settlement price at the end of every trading day. This is typically the weighted-average price over the last half hour of trading. After 15:30, Kite replaces the displayed LTP with the settlement price for MTM purposes.

How to fix LTP showing zero on the Kite marketwatch

Wed, 20 May 2026 00:00:00 +0000

Zero LTP on a Kite marketwatch row almost always means the contract has not traded recently, not that Kite is broken. This guide walks through the common causes ordered by frequency.

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.

LTP difference between Holdings and marketwatch on Kite

Wed, 20 May 2026 00:00:00 +0000

A common point of confusion: the LTP shown for a scrip on the Kite Holdings tab does not exactly match the LTP shown for the same scrip on the marketwatch . The discrepancy is small (usually a few paise to a few rupees) but is regularly reported as a “bug”. It is almost always explainable by one of a handful of causes.

The four common causes

1. Refresh timing

The marketwatch streams live ticks at sub-second frequency. The Holdings tab refreshes the LTP for each row at a slightly slower cadence (every few seconds, throttled to reduce server load). A quote that ticked one second ago will appear on the marketwatch immediately and on Holdings after a small delay.

LTP difference between marketwatch and chart on Kite

Wed, 20 May 2026 00:00:00 +0000

A common observation: the LTP shown on the Kite marketwatch row for a scrip differs slightly from the LTP shown on the chart for the same scrip at the same moment. Usually a few paise to a few rupees, this difference comes from the way the two surfaces consume the exchange tick feed.

The two surfaces consume ticks differently

Surface	What it consumes	Refresh cadence
Marketwatch row	Real-time tick stream	Sub-second
Chart (TradingView or ChartIQ)	Aggregated OHLC bars	Bar-aggregated; live trade updates within the in-progress bar

The marketwatch displays the very last tick that arrived. The chart’s last bar updates with each tick within the bar’s timeframe (e.g., a 1-minute bar accumulates ticks until the minute closes), and the chart-displayed LTP is the price of the most recent tick consumed by the chart engine.