Power Platform Community Forum Thread Details

Due to a retention issue in power automate desktop, some executions get stuck without moving to a next step within the flow (this occurs at different points, indicating that it is not a flow issue).

In a call with Microsoft support, they suggested increasing the execution time limit of the flow in the queue and/or canceling the execution of the parent flow (cloud flow) given a certain delay. This second solution was implemented, but there is a problem because it does not consider the time that the Robot can stay in the queue waiting for a machine to execute.

Googling I didn't find a connector that could be triggered externally as an intermediate event in the stream. The idea is to have an intermediate event (webservice for example) that the RPA will invoke as soon as the execution of the Robot actually starts, thus giving continuity to the arm that will control the robot's execution timeout. Internally in Power Automate Desktop there is no such parallel flow logic.

Any suggestion will be very welcome.