Anomaly score check not evaluating after >4 scans

[janet-can]

The expectation is that an anomaly score check begins evaluating after a minimum of four, regular-frequency scans that gathered measurements. However, after multiple regularly-scheduled hourly scans of a dataset, the anomaly score check is still not evaluation.

• Why does it not show the "Last scan ended" value? The duration value in the other view attests to the fact that the scan did complete.
• The Scan success results are puzzling-- what does the value 11.54 for the Anomaly test indicate?

Ultimately, just can't get the anomaly score to yield expected output and we're not sure why.