Cloud Flow Run History in Dataverse
- Please note that, at the time of writing this article, this feature is still in preview.
- Preview features aren’t meant for production use and might have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
Quick overview
The Manage Cloud Flow Run History in Dataverse feature provides users with the ability to efficiently track, manage, and analyze the execution history of their Power Automate cloud flows directly within Microsoft Dataverse. The cloud flow run history records are stored in FlowRun table using Dataverse’s nonrelational database, elastic tables.
Please note that only solution cloud flows (solution-aware cloud flows), with their definitions in Dataverse, can have their run history stored in Dataverse.
The documentation for the Flow Run table/entity reference is here.
Storage use for FlowRun records
FlowRun data uses Dataverse database storage capacity. By default, flow run data is stored for 28 days (2,419,200 seconds).
Set FlowRun time to live (TTL)
In Dataverse
Setting the FlowRunTimeToLiveInSeconds value in the Organization table to zero stops all ingestion of new FlowRun records.
In Power Platform admin center
The FlowRunTimeToLiveInSeconds value in the Organization table can be set in the Power Platform admin center environments experience. To choose the FlowRun entity time to live that's used in an environment:
- Sign in to Power Platform admin center.
- Navigate to Environments.
- For the desired environment, open the Settings page.
- Select Product > Features.
- Under Cloud flow run history in Dataverse, set the FlowRun entity time to live retention value to 28 days (the default), 14 days, 7 days, or Disabled.
Clean up FlowRun records immediately
If your environment is low on storage, you can free up database space by configuring the TTLInSeconds value for specific FlowRun records. These records will be automatically cleaned up and permanently deleted within one to two minutes. Be certain the records are no longer needed, as deletion is irreversible.
Published on:
Learn moreWe can help you with Cloud Flow Run History in Dataverse
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Generative pages in model-driven apps: a practical guide
What generative pages are, where they stand in November 2026, the two ways to build them, the code they produce, and the limits to plan for.
Big Update — CRMJetty Dynamics 365 Portal Now Comes with Powerful New Integrations
Enterprise portals are evolving rapidly. They are no longer mere portals through which CRM records can be viewed. Portals are now expected to ...
Power Apps Code Apps in Practice: Recreating Model-Driven App Patterns
Power Apps Code Apps went from preview to general availability in record time. With that, Microsoft has sent a clear signal that it is taking ...
Use XRM type definition in your Javascript file
We implement Javascript webresource for form scripting (form onload, field on change,...). Our code need to follow the official document Xrm o...
Dataverse Functions Deep Dive
Microsoft released in 2024 Dataverse low-code plugins. The promise was great : writing plugins using low-code tools. No need to have developme...
Dataverse : Get Audit Storage by table
Dynamics 365 auditing feature logs changes made to records, allowing you to view the details of those changes at any time. Whenever a record i...
D365 Sales -2025 Wave release
In this post, we highlight the latest releases from Microsoft D365 Sales' 2025 Wave updates. For a detailed breakdown, click here. Public Prev...
10 Ways Dynamics 365 Calendar Boosts Productivity for Sales & Support Teams
In today’s fast-paced business environment, time is the most valuable resource for both sales and support teams. Managing appointments, meetin...