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.
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.
Restarting the Beacon Engine service (or restarting the beacon server) forces the rule details to be reloaded according to the current time zone.
This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R1.7 / Oct 2022 (Cloud), 2022 R2 (On Premises)