Once off timing works but appears incorrectly on the UI
Tony Sheehy 11 years ago • updated by anonymous 7 years ago • 2
On the home-page, a Once-off timing sits on 1 second remaining after it has run.
Additionally, the expiry timing still shows next run information, however it correctly does not run.
Customer support service by UserEcho
A filter is applied for expired timings, but the once off timing is only expired once it has run (which is correct). The UI now filters any timings which have a negative next run time. Timings that might have run (less than 0) will be represented in the statistics in any case.
Reassigned for confirmation of completion. This can be confirmed in the next incoming build.