Summary
In the Power Automate terminology, an action is the task that's started when a trigger is invoked: flows can have one or many actions, depending on what's needed to complete a particular flow. From a cloud flow standpoint, running a desktop flow is an action.
This article summarizes common action failures that may arise when running desktop flows.
Causes and resolutions
Please find below a list of the most common error codes of these scenarios, their root causes and the proposed resolution.
-
Your desktop flow failed to run with the error code "UIFlowParentFlowFailed" or the error details "Failure due to parent flow completion". This error has two common root causes:
-
The parent cloud flow has failed. This can be caused by the failure of another cloud flow action. Please check the parent cloud flow and resolve the issue.
-
The machine (or machine group)’s run queue is too big, or the connection usage has been throttled (because the connection is used too much). Check your connection usage and create a new connection to use in the desktop flow where you’re facing this error.
-
-
Your desktop flow failed to run with the error code "DesktopFlowsActionTimeout".
-
The desktop flow action failed because of throttling. This error code appears when too many desktop flows use the same connection. Check your connection usage and assign your desktop flows to multiple connections.
-
-
Your desktop flow failed to run with the error code "DesktopFlowsActionThrottled".
-
The execution of the desktop flow action exceeded maximum duration. Increase the time-out value that is set on the action or split the desktop flow into several shorter desktop flows.
-
