How insights and recommendations resolve
An insight and its recommended steps have separate lifecycles.
The insight represents a finding about a metric. Its recommendations represent decisions or work prompted by that finding. Completing, ignoring, approving, or rejecting one recommendation settles that step without rewriting its siblings.
Automatic resolution
Open findings are re-evaluated as new metric data arrives. When the metric recovers, FleetHQ can resolve the insight automatically. This is why the workspace says, These clear on their own when the metric recovers.
An opportunity in Not measured yet follows a related rule: it is no longer an adoption gap after genuine data begins reporting.
User decisions
The progress counter uses actioned or reviewed because every decision counts. Ignoring or rejecting a step settles it just as surely as completing or approving it.
A detector-only finding may also offer insight-level Got it and Not useful actions. Those close the finding itself rather than a child recommendation.
Queued findings
FleetHQ displays the most important findings first. Additional findings may remain queued. The queued count is not hidden work the user must find elsewhere; those findings surface as current ones resolve or are dismissed.
When the selected finding leaves the active list, the workspace keeps the reader moving by selecting the next available finding.