I've just seen the following in a post from J Davis:-
"You would just need to add a time based trigger within your main scan. Never use TimeIntoInterval within a SlowSequence; it wouldn't trigger."
I'm interested as I have seen this in a lot of logger programs that seem to work fine, can someone explain?
TimeIntoInterval looks at the scan time(timestamp of when the scan started) and only evaluates as true when the time is an exact match. Scans in a slow sequence start after the main scan has finished. So for example, a 5 minute slow sequence may actually start 200 milliseconds after the start of the 5 minute interval. Since the scan time of the slow sequence is 200 milliseconds behind, TimeIntoInterval looking for 0,60,Min will never trigger. The time is never an exact match.
TimeIsBetween can be used in a slow sequence, since it checks if the time is within a range. It evaluates as true for more than one scan.
Per request of another engineer, I did some testing of TimeIntoInterval within a slow sequence. Current OS versions time stamp the slow sequence scan in a way that makes TimeIntoInterval work in most cases.
The only case I could get TimeIntoInterval to skip was when I skipped slow scans.
It is still recommended to use TimeIntoInterval within the main scan. Since we use the slow scan for processes that take a relatively long time, there is a good chance of skipping one.