Flow Update Recency Insight

Overview

The Flow Update Recency report helps you to monitor the freshness of the content across your organization so that you can proactively prioritize and plan for updates to your content.

What this report shows

Flow Update Recency graph

The bar graph shows how recently the flows in the selected entry point were last updated. Each bar represents an update interval, from 0-30 days ago to >365 days ago. In this report, "last updated" means the date of the last published change to a flow.

Last published change by flow

Below the bar graph is a table that displays all flows in the entry point. Click a bar in the graph to filter the table to display only the flows for that interval. Click on that same bar to deselect it and return to the 'all intervals' view.

The table includes the flow name, the date it was created, and the date it was last updated. These include links to view the flow, and the change request corresponding with the date created or updated respectively.

Note  The "last updated date" for a flow reflects the last date a change was published to that flow, but does not indicate the nature of the change; i.e. the last update could reflect a complete process revamp or a simple typo correction.

Exporting the update recency data

Click Export CSV to download a CSV that shows the following metadata for each flow in the selected entry point:

• entry point ID and name
• flow ID and name
• change request ID and date the flow was created
• change request ID and date the flow was last updated

If you have filtered the table to a specific interval, the CSV export will only include flows that were last updated in the selected interval.

The columns in the Flow Update Recency CSV export include:

Why it’s important

Identify stale or unmaintained flows that haven’t been updated within an expected timeframe so that you can review or retire content before it becomes a liability. This helps to reduce the risk of outdated guidance being relied on by human or AI agents. 

When you are able to plan update work, you can prioritize which flows need attention first, allocate resource time effectively, and align updates with policy changes, system releases, or peak operational periods.

Insights you can draw from this report

• Identify higher-risk content: Flows in the >365 days    range are most likely to be outdated and should be prioritized for review - especially if they support critical operations or compliance.
• Spot uneven maintenance patterns: A mix of very recent and very old flows may indicate inconsistent ownership or gaps in your content governance.
• Assess content health by entry point: If most flows fall outside your expected update window, it may signal that the entire entry point needs a structured review cycle.
• Validate update activity vs. real change: Since “last updated” reflects any published change (including minor edits), use this report as a starting point - not proof that the process itself is truly up to date.
• Plan and sequence update work: Use the distribution to batch updates (e.g., tackle all >365-day flows first) and align work with upcoming policy or system changes.