Known Issue: Rules may not run at the correct scheduled time until the beacon engine service is restarted after the beacon's time zone or daylight savings setting is changed (IOJ-2228184)
Known Issue: Rules may not run at the correct scheduled time until the beacon engine service is restarted after the beacon's time zone or daylight savings setting is changed (IOJ-2228184)
Summary
After the time zone of a beacon is changed (including daylight savings starting or ending), discovery and inventory rules may not run at the correct scheduled time until after the Beacon Engine service is restarted.
Details
The time rules should run is stored internally as a UTC value. If the time zone of the beacon is changed, the UTC value now corresponds to a different local time and the rules run at the incorrect time.
Workaround
Restarting the Beacon Engine service (or restarting the beacon server) forces the rule details to be reloaded according to the current time zone.
Fix status
This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R1.7 / Oct 2022 (Cloud), 2022 R2 (On Premises)
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.
