Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The process map builds on the robust monitoring and observability features of the Automation Center. This feature enhances transparency by showing process-centric flow dependencies and offers an intuitive, streamlined experience for monitoring and troubleshooting end-to-end automations.
Navigate the process map
The process map makes troubleshooting and monitoring in Power Automate more efficient and transparent. It shows the main orchestrating flow and all its child flows invoked during a process run. When a process map is created, it considers structural details like conditions, so it can show flows that are part of the process but didn't run because of certain conditional logic or errors. This helps you understand how a problem in one part of the process can affect other parts and take the right countermeasures to fix issues.
When you select a flow box on the map, its side panel opens, providing detailed contextual information on run, connection, and design-time properties. This panel lets you efficiently scan through the run history and better understand the root cause and impact of errors without navigating to each run from the flow details page or the Automation Center. This efficiency is especially helpful when troubleshooting flows called in a loop by their parent, potentially producing tens or even hundreds of runs per process run.
Important
Process map is considered as a premium capability. Flows that are part of a process map are considered as premium flows, and require an appropriate license. Learn more in Power Automate licensing.
Runs view
The Runs view displays the process map for a specific flow run. It highlights the exact path taken during that run and shows the status of each step, helping you analyze what happened in detail.
Overview view
The Overview view presents the overall process map, aggregating all possible paths, and steps for the flow. This view is useful for understanding the full scope of the process, regardless of individual run status.
Insights view (preview)
[This section is prerelease documentation and is subject to change.]
Important
- This is a preview feature.
- Preview features aren’t meant for production use and may have restricted functionality. These features are available before an official release so that customers can get early access and provide feedback.
- For more information, go to our preview terms.
Insights (preview) gives you a process‑level view of reliability and performance key metrics, visualizing error clusters, trends, and enabling a one‑click integration with Process Mining. This allows you to deep dive into advanced insights such as variant (route), bottleneck, and deeper route analysis, all integrated within the process map experience. It helps you spot trends and issues faster, prioritize fixes, and share a consistent view across makers, operators, and Center of Excellence (CoE) teams.
The following sections list the prerequisites for viewing and using process-centric insights in the process map. If you only need basic insights, review the Prerequisites section. For using advanced insights, make sure you also meet the requirements in the Advanced insights prerequisites (using process mining) section.
Prerequisites
- Power Automate Premium license with access to an environment.
- A process map is created for the top‑level cloud flow.
- The environment stores run history in Dataverse (Automation Center).
- You have permission to view runs for the flows included in the process (for shared/admin scenarios, some flow names might appear masked).
Advanced insights prerequisites (using process mining)
- Process Mining capacity of at least 50MB is available in the environment.
- You have the required permissions to manually create new Process Mining processes in the environment.
Note
Advanced insights use Power Automate's Process Mining capabilities and consume from your Process Mining capacity in the tenant. Before you enable advanced insights across the organization, make sure sufficient capacity is available.
View Insights (preview)
Open insights by selecting the Insights (preview) toggle on the process map. Insights are organized into two tiers:
- Basic insights: Enabled by default. Built‑in reliability and performance views computed from run history.
- Advanced process insights: Opt-in. One‑click integration with Process Mining for deeper route/variant, bottleneck, and correlation analysis.
Basic insights
Basic insights have a single Overview tab scoped to the selected time range.
| Metric | Description |
|---|---|
| Runs | Total number of process runs in range |
| Failed runs | Number of runs that ended in failure |
| Failure rate | Percentage of runs that failed |
| Average run duration | Mean end‑to‑end duration per run |
| Mean time between failures (MTBF) | Average time between two failures; for example, if your flow ran for total 100 hours in the selected timeframe and had five (5) failures, the MTBF is 100 / 5 = 20 hours. |
Panels
| Panel | What it shows |
|---|---|
| Flow runs error trend | Error rate overlaid with run volume across time to reveal spikes and patterns |
| Top flow error codes | Most frequent error codes with counts to accelerate root‑cause analysis |
Advanced process insights (Process Mining)
Enable advanced insights to unlock enterprise‑grade analytics powered by Process Mining without the need for manual exports or lengthy data preparations.
To enable advanced insights:
- On the top of the screen, select Insights (preview).
- In the side-panel, select Enable advanced insights.
The following table explains what you get with advanced insights.
| Metric | Description |
|---|---|
| Runs | Total number of process runs in range |
| Routes | Distinct process routes (variants) observed in range |
| Avg run time | Average end‑to‑end duration per run |
| Errors | Number of runs that ended in error |
| Error rate | Percentage of runs that ended in error |
Advanced panels
| Panel | What it shows |
|---|---|
| Process runs error trend | Error rate overlaid with run volume across time to reveal spikes and patterns. |
| Top flows by error volume | Flows ranked by number of error outcomes; use View all to expand the list. |
| Top error details | Clusters failures by error code/reason with percent of impacted runs and counts. Expand an error to display details such as most impacted route that will show on the process map and also see error first/last seen timestamps. |
Note
- In high‑volume environments, preparing insights for large run sets can take longer.
- Make sure you have enough process mining capacity assigned in the environment.
- To disable Insights (preview) for an environment, turn off Enable production-ready preview features for Power Automate Automation center in the Power Platform admin center. This setting disables all other Automation Center preview features.
Troubleshooting
| Issue | Resolution |
|---|---|
| I selected insights view, or enabled advanced insights, but don't get metrics data | Make sure you set the correct date filter for your scenario. Also, if your flow runs are less than 48 hours old, they aren't considered for the analysis yet. Metrics and data appear only after the runs are older than 48 hours. |
| Can't enable advanced insights | You likely lack Process Mining permissions or capacity. Ask your admin to grant access and ensure capacity is available in the environment. |
| Problems with advanced analytics panel | If you accidentally changed the process mining process within the Process Mining suite that now causes issues in the process map's advanced analytics panel, you can delete the project in Process Mining and re-enable advanced insights. CAUTION: Do this only if the changes weren't intentional, as deleting the project removes all modifications you made. |
Create or view a process map
To create or view a process map in Power Automate, you have two options. They're described in the following sections.
Option 1: Use the runs tab
- Go to the Automation center and select the Runs tab.
- Hover over a top-level flow run and select the process map icon next to the name to generate the map.
- If this is your first time using the process map icon, you're prompted to provide a process name.
- Select Create.
Option 2: Use the process map tab
Go to the Automation center and select the Process map tab.
The map displays a drop-down box in the upper left corner that lists the processes you have access to.
In the drop-down menu, select the ellipsis (three dots) and select Create a new process map.
Once the process map is generated in the backend, the process name appears next to the flow name in the run list. If the process column isn't visible, you can add it by using the Show/hide columns link located at the top-right corner of the runs list.
Note
- Depending on the volume and complexity of child flow dependencies of your flow, this process could take up to 10 minutes to complete.
- You can close the dialog message, Analyzing flow dependencies, and return later to view your runs in a process-centric view.
Rename or delete a process map
To rename or delete a process in Power Automate, follow these steps:
Go to the Automation center and select the Process map tab.
The map displays a drop-down box in the upper left corner that lists the processes you have access to.
To view the list of processes, select the ellipses (three dots) next to the process name in the drop-down menu.
From here, you can rename or delete your process.
Note
Deleting or renaming a process doesn't delete any of the flows or runs associated with the process.
Process map visualizations
| Icon | Description |
|---|---|
|
Represents the start and different end states of a process. |
|
Represents a cloud flow. |
|
Represents a desktop flow. |
|
Represents a loop scenario where a parent flow calls a child flow n-times. |
|
Represents the total number of times various parent flows ran this flow. Each flow instance is triggered by a different parent flow run, instead of being repeatedly called within a single parent run loop. |
|
Represents a conditional or optional flow. This means that the flow connected by the dotted line isn't always executed, but depends on certain conditions being met. |
|
Represents a missed or skipped flow based on conditional logic or an upstream error. |
Known issues and limitations
- Creating and viewing process maps requires users to have the Environment Maker or similar roles with sufficient privileges on the business process table.
- Runs for co-owned or shared flows aren't supported yet, which means flows shared with users don't display for them.
- Users with broader access (like admins or CoE teams) might see 'Unknown flow' as the flow name. This happens if the flow isn't explicitly shared with them or is deleted.
- Process maps for top-level desktop-flows aren't supported yet.
- Parallelization features (for example, cloud flow 'Apply each' with concurrency or 'RunAfter' customizations) aren't visually represented. Such child runs appear in the order they were defined.
- Dynamic flow selection using a formula (instead of the standard picker) isn't supported. Such child flows are ignored.
- For any given run, only the first 100 child flows are loaded. For example, if flow A triggers 150 instances of flow B, only the first 100 are processed.
- Process map definitions might not remain fully current if more than 50 levels of child flows exist.
- Runs that were created with a previous structure of the process map don't show flow runs of flows that aren't part of the current map anymore.
- Generating a process map with moderate to large dependencies can take up to 10 minutes. During this time, an 'Analyzing flow dependencies' dialog is shown.
- Updates to a process map after its dependent flow structures are modified might take several minutes, and there’s currently no visual indicator to show the map is updating.
- Although process maps are solution-aware and can be exported or imported to downstream environments, they can't currently be created directly from within the solution explorer.