Known Issue: System Tasks may not show the most recent run for all beacons from different time zones (IOJ-1904459)
Known Issue: System Tasks may not show the most recent run for all beacons from different time zones (IOJ-1904459)
Summary
Beacon rules to execute various discovery and inventory tasks are run by each beacon at the set schedule time in the time zone of that beacon. In a system with beacons in different time zones, rules end up executing at different moments in time.
This can create a situation on the System Tasks page where tasks remain being shown with an "in progress" status waiting for a task to be executed on beacons across all the different time zones. In extreme cases, tasks may never end up being reported with a complete status.
Workaround
There is no direct workaround to this behavior. Be aware that tasks will be running on beacons at different times (according to each beacon's time zone), and reporting accordingly. Task details can be expanded on the System Tasks page by clicking the "+" icon next to the task to see additional details about which beacons the task has executed on.
Fix details
The fix for this issue is to change the System Tasks page so that a separate task is displayed with an appropriate status reported for each individual beacon, rather than having a single task with an aggregated status covering all beacons.
Fix status
This issue has been fixed in the following FlexNet Manager Suite releases: 2021 R1.4 / Mar 2022 (Cloud), 2022 R1 (On Premises)
Other information
Affected components: Discovery, Remote execution, Web UI
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.
