I’m using some Streak scanners on Nifty weekly options. In Kite, when the 5-minute Nifty Index chart finishes forming a 5-min candle, Streak doesn’t immediately give alerts. There’s a delay of about 36 seconds from the end of the candle.
Please clarify how to eliminate this delay.
Hi @jaydivanji
Do note that Streak takes an average time of 20~30 secs to calculate the input values(Indicator values/ Entry conditions and other parameters) to produce an output. It is not possible to maintain the accuracy and keep the alert delivery time even less due to various reasons. The key reason is the data latency in candle formation and retrieval from the exchange data sources itself.
If we hurry and generate alerts without confirming multiple times that the candle is formed and all ticks have been accounted for in forming the candle, the signal might be incorrect and later may not match with the charts or scan results, leading to more confusion and unreliable analysis. You can refer to the below link to learn more about this-
https://tradingqna.com/t/why-is-ohlc-data-different-on-live-charts-and-marketwatch/16528/3?u=streak
Hope this clarifies the doubts.
Thanks for the clarification.
this is one of worst thing in streak " the data delay"
my data delays almost 1 mint
so after the 1 mint its useless
( but one thing i admire alot in streak it gives 90% accurary signal one of best also )
look at the image 56 second delay
@Deep_Prajapat Please share the scanner links along with the alert frequency settings so that we can verify it on our end.
My alert frequency setting set in 1 Mint
and scanner running on 1 Mint TF also
@Deep_Prajapat We’d like to highlight that the signals generated by Streak are 100% accurate as per the scanner conditions configured, and they trigger exactly when those conditions are met. However, if you’re noticing any delay in receiving alerts, please note that there can be a brief delay of a few seconds after candle close before the signal is triggered. This is due to factors such as data processing time, network latency, browser performance, or device-specific limitations.
As mentioned in our previous communication, to proceed with a detailed analysis, we kindly request you to write to our Support team at [[email protected]] with the scanner link and scan logs.
We appreciate your understanding.
