This is a recurring problem.
When a new session begins (15:30 cst) the hi/lo for the previous session is not being "reset".
Right now (at 15:38cst) the high low range for "AB m6" is shown as 742.90 / 729.20. This is the hi-lo for the session that ended at 15:15cst.
I have brought this up with phone-in tech support many times and all that happens is that it gets corrected for the then current session and then tomorrow or a few sessions later -boom- it happens again.
Why is it happening to "AB m6" and no with any other contracts?
Can someone PLEASE correct this issue. I image it needs to be done programatically rather than brute-force overriding the erroneuous data on an ad-hoc basis.
When a new session begins (15:30 cst) the hi/lo for the previous session is not being "reset".
Right now (at 15:38cst) the high low range for "AB m6" is shown as 742.90 / 729.20. This is the hi-lo for the session that ended at 15:15cst.
I have brought this up with phone-in tech support many times and all that happens is that it gets corrected for the then current session and then tomorrow or a few sessions later -boom- it happens again.
Why is it happening to "AB m6" and no with any other contracts?
Can someone PLEASE correct this issue. I image it needs to be done programatically rather than brute-force overriding the erroneuous data on an ad-hoc basis.
Comment