Beacons Load Last Heard History is Inconsistent with the Beacons pane, in a VarAC Cluster.
The history loads entried from multiple instances, whereas the live Beacons history only displays the beacons on the current instance number.
Suggested Fix
I suggest when an instance loads history, the history should select for display only the entries heard by that instance number, not from other instances. The rest should be filtered out and excluded. I.e. it should restore the same entries that were displayed previously.
In any case, the behavior should be consistent!
Test
Close and then reopen an instance and ensure it shows the same entries as before, and not additional entries leaked from other instances.
Screen Capture
Added a feature that beacons/CQs are written with an instance number to the database. while in cluster enabled, upon startup, each instance loads only its own records.