(Attended) PAD Flows triggered by scheduled Flow no longer start

[Cayshin]

EDIT - Nevermind. I guess it's just Microsoft's servers going really really slow. I let the Scheduled Flow sit there running for 20+ min and it eventually started the PAD flow.

Starting this afternoon, none of my scheduled PAD Flows will start.

I can see the running process of the Flow is going, but when it hits the "Run a flow built with PAD", it sits on it and nothing ever happens.

This is true for all my PADs started via a Flow.

I've updated the Gateway and updated PAD, but the PAD Flows still won't start.

The Gateway shows it's up and active.

Is there some way I can check why it's getting stuck? Is anyone else running into this issue today?

Thanks

[amamidwar23]

hi @Cayshin 

The same happened with me either , i takes time when triggered from cloud flow .

if you trigger it from browser from the same VM where you have flow created , it take less time 

Thanks,

AR

[Cayshin · Accepted solution]

I think it may have been lingering effects from the Service Interruption mentioned in MO263732: 

"June 22 - Users in Canada may have degraded service functionality across all Microsoft 365 services" (although, I'm in MI).

 

Everything is working as expected today, but your tip is good to know. Thanks! 

[Ahammad_Riyaz]

Hi @Cayshin 

Now we having machine key adding update like uipath,so can u plz on tat

Regards

Ahammad Riyaz