Community pattern keeps Power Automate run history past 28 days
Reviewed by Helen Jones
A Power Platform community blog published around 8 July 2026 shows how to keep cloud flow run history longer than the usual 28 days. The method uses Cloud Flow Run Metadata stored in Dataverse rather than relying only on what the Power Automate portal shows. Makers can inspect the current retention setting, change FlowRunTimeToLiveInSeconds, pull the stored run metadata, and build a simple view of total runs, successful runs, failed runs, and success rate. The portal history itself still defaults to 28 days. The longer trail lives in the metadata. This is a documented configuration pattern from the community, not a new Microsoft product feature. It needs Dataverse and the right environment permissions.
Before this pattern was spelled out, many live flows left makers with a hard cut-off. Run history vanished after about a month. When an approval, SharePoint update, or Teams notification failed weeks later, the evidence was often already gone. People fell back on screenshots, manual exports, or guesswork from incomplete run history. What changes is the option to treat run data as something you can keep and chart, not only browse for a short window. That helps longer troubleshooting, trend checks, and basic reliability questions. The catch is real: without Dataverse access, clear ownership, and a plan for who maintains the dashboard, the 28-day limit simply moves into a custom setup that can still break when the maker leaves.
Analysis
Treat this as a reliability option to investigate, not a weekend DIY project. List the production flows where a failure after day 29 would hurt, then ask your environment admin whether Cloud Flow Run Metadata and the TTL setting are available and who will own a simple success-or-fail view if you turn longer retention on.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Community pattern keeps Power Automate run history past 28 days", Collab365 Spaces. 2 sources referenced.