Cloud Flow w/ Desk Flow Timeout Handling

(0) Share

Report

Posted on by Andre89V

Hi Everyone,

First time posting a question, hope to get the etiquette right

I have several Scheduled Clod Flows that run Desktop flows, in unattended mode on Virtual Machines:

what I'm been trying to do, and aiming for, is when a Desk Flow run fails or goes timeout (already set in the setting) I'd like to kill the mentioned run (only the Desk flow) and launch another Desk Flow run (let's call it a retry), that at least for 2 times.

The problem occurs with the Timeout: the Configure run after "Has failed or timeout" works, "Desk Flow retry run" stars but the "timeout one" keeps running, occupying the Virtual Machine forever and queuing the scheduled flows

Anyone has any suggestion?

Already tried using a parallel "Terminate" action, but that will kill the all Cloud Flow

Thank You all

Categories:

Power Automate Desktop

All responses (3)

Answers (0)

Sort by

VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Andre89V

Could you do the retry logic within the Desktop Flow itself?

Meaning - Add a On block error where you think the error occurs in the Desktop Flow.

When an error occurs, you can use the Run desktop flow to call that another Flow that you already have.

(Instead of another Flow you can also have a Subflow within the same Desktop Flow and call that using Run subflow)
Andre89V 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

Thank You for your input

Seems like I cannot call the same Desk Flow inside itself and there are no time actions to set, moreover I can put a On Block Error but I'd like to have something related to a timeout, cause it's difficult to prevent or script all errors

Another user with the same problem:
Timeout to stop running desktop flow · Community (powerautomate.com)

Thank You
VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Andre89V

Seems like I cannot call the same Desk Flow inside itself

I had thought that you had mentioned about calling another flow using this statement -> like to kill the mentioned run and launch another Desk Flow run

Therefore, I have suggested Run desktop flow

If you want to call something from the same Flow you can either make use of Labels so that the Flow execution starts once again from where you want it to start.

Or you can also make use of Subflows in which case you can use Run subflow action.

cause it's difficult to prevent or script all errors

If you have a Try-Catch like functionality using the On block error, then no matter anywhere the error is, it will be trapped and then you can redirect the Flow using any of the above mentioned approaches.

I understand your requirement about the timeout but since there is nothing like that as of now you might have to go with a backdoor entry solution like the above.