From filters, you can select a dedicated version and see machines that are using this version. This feature is useful to understand which machines require updates (you should update your application regularly). Versions on machines: This card displays for each version of Power Automate for desktop, the number of machines that use this version. If you have more machines in your environment, use the filters to reduce the current selection. There is a limit of 40 connection statuses displayed at one time. You can select the machine name to reach its details page. In the pane, you can see all the machines per connection status. If you want to see machines that are disconnected, select See more. Connection status: This card displays the connection status of your machines (connected, disconnected, action needed).These pivot tables provide information about the number of machines, groups, connection status, Power Automate for desktop versions installed on machines, and lists of machines and machine groups. You can use the Machines section to monitor your machines and machine groups. Machines: Monitor your machines and machine groups Select the dropdown menu of the table to display the type of pivot you prefer. In addition to trends per error, the chart can display trends per desktop flow and machine. These trends can help you to identify if an error started to appear recently or several days ago. You can select each machine name to display its details page.Įrror trends: This chart displays daily trends for errors in desktop flow runs. Top machine failures: This card displays information about the machines on which desktop flow runs failed most frequently. For example, if a cloud flow contains two desktop flows and these desktop flows failed two times each, you'll see this cloud flows with a count of four errors. Top cloud flows with failed desktop flows: This card provides a list of cloud flows that are the most impacted by failures in desktop flows. You can select each desktop flow to display its details page. Top failed desktop flows: This card displays the desktop flows that failed the most in your environment. If you can't see a specific error in the card, select the All errors filter, and then choose the error that you want to see. Top errors: This card displays the errors that occur most frequently during your desktop flow runs. Optionally, you can select another time period and filter on specific errors. These pivot tables provide information about desktop flows, cloud flows, and machines in which errors occurred, allowing you to view details to identify the source of errors.īy default, this section displays the desktop flow run errors for the last seven days. You can use the Errors section to identify the most common errors that occur while your flows run. Last desktop flows runs: This card displays the latest completed desktop flows runs. If you want to review specific desktop flows, select them in the appropriate filter. For each presented desktop flow, the card gives details about the run mode (attended, unattended or local) and the run status (successful, skipped, failed, canceled). Top desktop flows runs status: This card presents the desktop flows that ran the most during a dedicated time period. Use this chart to quickly identify if there was a particular issue during a dedicated time period, such as too many failures and low number of runs. Run status – Trends: This stacked area chart helps you understand how your flows work across time. If no desktop flows run for one or several days, the corresponding data aren't available in the table.ĭesktop flows completion status: This donut chart displays the proportion of desktop flows that succeeded, failed, or got canceled. You can find information regarding each table in the following list:Ĭompleted desktop flows: This card provides the number of desktop flow runs in a selected period of time.ĭesktop flows runs and error rate: This chart shows the number of desktop flow runs and the error percentage by date. The Last runs section provides graphs and tables to get meaningful insights about your desktop flow runs, such as the number of runs, the percentage of errors, and the run modes. Cloud flows aren't saved in Dataverse, and environment admins need to get access to the flows to read details about them. If a cloud flow appears as private flow, it means that it isn't shared with you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |