<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Alert Not Triggered on WebNotes</title><link>https://v2.webnotes.in/tags/alert-not-triggered/</link><description>Recent content in Alert Not Triggered on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/alert-not-triggered/index.xml" rel="self" type="application/rss+xml"/><item><title>How to fix a Kite alert that did not trigger</title><link>https://v2.webnotes.in/how-to-fix-alert-not-triggered-kite/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-fix-alert-not-triggered-kite/</guid><description>&lt;p&gt;A Kite &lt;a href="https://v2.webnotes.in/kite-alerts/" rel="nofollow"&gt;alert&lt;/a&gt;
 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 &lt;a href="https://v2.webnotes.in/trigger-vs-limit-price/"&gt;LTP&lt;/a&gt;
 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.&lt;/p&gt;</description></item></channel></rss>