Flow Trace shows you what Power Automate can't.
Flow Trace is a Dynamics 365 and Dataverse tool from RautingTech. Paste a record ID and it shows every cloud flow, system job, audit entry and plugin that touched that record, in order, with the cause named. It runs inside your own Azure subscription.
Flow Trace in 62 seconds
Paste a record and see everything that touched it.
Pick the night you've had. The data below is a sample, so nothing here touches a real system.
Sample data. Real traces run inside your own Azure subscription.
Which flow changed this record?
Power Automate keeps run history per flow, and Dataverse's flow run table has no column for the record a run touched. So you have to know which flow did it before you can look. Flow Trace builds the missing index and joins every run to the record it touched.
Why does this flow keep failing?
Loops, missing error handling and unbound connection references, ranked by what blocks a release. Every rule cites the Microsoft documentation it rests on, so findings are facts rather than opinions.
Why does a failed flow say Succeeded?
Because a Catch scope handled the error and the run ended normally. Flow Trace samples the steps of successful runs and flags the ones where a step failed, a business step never ran, or the flow quit early.
Is it safe to deploy?
A plain verdict for every solution in every environment. It finds the edit someone made directly in Test over a managed solution, the one that would make your next import quietly change nothing.
How is Flow Trace different from Microsoft's built-in tools?
Microsoft's tools each show one source, one flow or one table at a time. Flow Trace starts from the record and joins them. Keep the built-in tools; Flow Trace works alongside them.
| Question | Power Automate run history | Dataverse audit history | Plugin trace log | CoE Starter Kit | Flow Trace |
|---|---|---|---|---|---|
| Start from a record ID | No, start from a flow | Yes, field changes only | No | No | Yes |
| See every flow that touched it | One flow at a time | No | No | No | Yes, on one timeline |
| Flag runs that hid a failure | No, shows Succeeded | No | No | No | Yes |
| Detect flows that trigger themselves | No | No | No | No | Yes |
| Find hand edits over managed solutions | No | No | No | No | Yes, per environment |
| Estate inventory and adoption | No | No | No | Yes | Not its job |
| Where it runs | Microsoft cloud | Dataverse | Dataverse | Your tenant | Your Azure subscription |
Last updated October 29, 2026. Based on the built-in tools as documented by Microsoft. Run history retention is limited; Flow Trace keeps its own index in your storage.
It runs in your Azure. We never see your data.
Read: run history and metadata. Never writes to flows, records or solutions.
Publishes signed releases. Holds none of your trace data.
- F-01Read-only in Dataverse
A reader role with each privilege listed. Audit history stays opt-in per table.
- F-02Payload values never stored
Trigger values are read in memory to find the record and then discarded.
- F-03Signed, admin-approved updates
Releases are verified against pinned keys before install. Nothing updates on its own.
- F-04Tamper-evident audit
Sign-ins, settings and licence events are hash-chained, so an edited entry shows exactly where.
Pricing is per environment, never per seat.
Priced per monitored environment. At launch it's billed through Azure Marketplace, on the Microsoft invoice you already pay. No per-user fees.
What do I need to install it?
An Azure subscription, and a Power Platform admin for one consent screen. Early-access installs are set up with you; once listed on Azure Marketplace, Azure builds the install in about five minutes.
Does it work with the CoE Starter Kit?
Yes. Keep the CoE Kit for governance and inventory. Flow Trace is the incident tool it doesn't include.
Can RautingTech see our data?
No. Flow Trace runs in your subscription and stores its index in your storage account. RautingTech publishes signed updates and nothing comes back.
Which Dynamics 365 apps does it support?
Anything on Dataverse: Sales, Customer Service, Field Service and custom model-driven apps, and the cloud flows that act on them.