0
Fixed

Exclusion timings return true at the end of an exclusion period

Matthew Clark 6 years ago • updated by anonymous 3 years ago 2

While the next run information is always correct, the CheckDue function of exclusion timings starts returning true if an exclusion period ends, rather than at the appropriate next run time. This is because the internal timing's NextRun property is not updated when an exclusion period is in effect, and as such will retain a NextRun value in the past, causing it to run on the next CheckDue call outside of the exclusion.

Affected Versions:
Fixed by Version:

This has been resolved with extended unit tests that all pass, but this should also be verified in the Identity Broker and FIM Event Broker engines

To test this, set up a schedule with an exclusion period, and confirm that the operation list/connector does not run when the exclusion period ends, but rather the next run time that is outside the exclusion period (eg. if 12:00 to 12:05 is excluded and it runs every 3 minutes from 12:00, it should run at 12:06 and not 12:05)