The new Kite TSL feature: In case of a Nifty Contract, does it use the contract tick stream or does it use a less frequent interval? I’m finding that my back test that uses historical 1m data for the same Nifty Contract, hence considering all highs and lows, does not match the Kite TSL trigger. It fires much earlier, about 45 minutes earlier. The only conclusion I can make is that Kite TSL does not go through each tick price of the contract because the Low that should have exited it as per back test did not trigger it. So I suspect, it checks less frequently and misses the highs and lows that might have occurred between checks. Please confirm.
GTT TSL is designed to work on the ticks recorded or displayed live on the system, and not on a fixed polling interval. When a day's high or low breaks on the chart, that value gets revised or reprinted afterward. This reprinted value may not exactly match the tick that was actually received on the server in real time. Since TSL trailing and triggering is based on the actual tick received, a mismatch between a backtest (which may use settled/reprinted high-low data) and the live trigger can occur for this reason.
