Below, you can see some implications for various periods when change detection isn’t running.
Minutes to Hours
If change detection cannot run for a few minutes to a few hours, there should not be a noticeable impact on your Flow Metrics as the agent only queries your tools once every four hours.
Simply put, if change detection isn’t running during a period when Viz isn’t collecting data, there is no data loss.
If change detection cannot run for multiple hours, there is a possibility that a change will be missed. However, as soon as change detection resumes, Viz will receive the accurate data.
For the most part, even if you group your Flow Metrics in Viz at the most granular level, you should not see any difference in the data.
If change detection cannot run for a day, you may notice some changes in your Flow Metrics, although it’s unlikely. If grouping your Flow Metrics by week, your completed work will still contribute to the same week, even if delayed by a day, thus not impacting your Flow Metrics.
Days to Weeks
If change detection cannot run for multiple days to weeks, there will be a noticeable change in your Flow Metrics.
Viz will assume that artifacts remained in their last known state for the duration of the outage. Once change detection resumes, Viz will perceive any changes to the artifact states as occurring at that time — resulting in inaccurate Flow Metrics. You’ll likely see a Flow Velocity® spike on that day, as Viz will interpret any artifacts that moved to ‘Done’ during the outage as closing on the date when change detection resumed. This will also display longer Flow Times than are truly accurate.