stock777 Posted June 7, 2021 Report Share Posted June 7, 2021 (edited) Not sure if this is ONLY an after hours problem, but on % move alerts, getting triggers on late prints that are well out of the current bid/ask range ( by $$$'s ) , even thought that setting is chosen. Edited June 7, 2021 by stock777 Quote Link to comment Share on other sites More sharing options...
stock777 Posted June 8, 2021 Author Report Share Posted June 8, 2021 ?? Quote Link to comment Share on other sites More sharing options...
Mike Medved Posted June 8, 2021 Report Share Posted June 8, 2021 lemme take a quick look at code... Quote Link to comment Share on other sites More sharing options...
Jerry Medved Posted June 9, 2021 Report Share Posted June 9, 2021 there seems to be a gap in expectations. The way it is working if that option is selected, then the price used for the alert is as follows * if the LAST is inside the spread, the LAST is used. * if the LAST < BID, the BID is used. * if the LAST > ASK, the ASK is used. the wild LAST value should not trigger the alert unless the bid/ask are also way out of range. If that is not the case, can you give specifics? Quote Link to comment Share on other sites More sharing options...
stock777 Posted June 10, 2021 Author Report Share Posted June 10, 2021 No , I understood that the wild last value should not trigger the alert. The bid /ask were quoted normally at the time Ill try to capture a case of it . Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.