Unattended robot halts actions mid run.

[MRJ86]

Hi all

I have an issue with one of my robots. Sometimes when its running, it does not stop again, as seen on the picture below. The robot starts and runs for 3min and reached a an "Open Outlook" activity, which is standard setting and has no policy for retry set. Then it just waits for 1 hour (untill I chanceled the parent flow):

I have seen this issue a couple of times since last week, where we updated PAD to 2.42.317.24061. Worse case it waited for more than 4 hours, which stops all of our other robots 😞 

Hope you can help me 🙂

Best regards

Mikkel

[Chetan_Ninghot]

Hi,

While running any process on an unattended mode , if any action failed its not able to take more time like 1 hour

have you handle exception on PAD level and Cloud level into your unattended process.

I think its may be issue into the latest version of PAD (2.42.317.24061)

(Note:- if you got your solution you can mark as solution and gives kudos)

Thanks & Regards

Chetan Ninghot

[MRJ86]

Hi Chetan

I have not set up error handling around the point where the robots "idles". But no errors is thrown, nothing just happens.

My temporary fix is to set the "Action Timeout" to 10min in my Cloud flow that starts the robot, trying to limit the time it can do nothing. But I would love a fix to the problem and not the handling the effects of it 😉 

Best regards

Mikkel

[Deenuji]

@MRJ86 

Did this problem occur in the previous version? If not, consider reverting to the previous version to verify if the issue persists. If the previous version functions correctly, please report this problem to Microsoft.

Before submitting a ticket or downgrading, ensure error handling is incorporated for each step to determine if any errors occur. If no errors are encountered, proceed with submitting the ticket and downgrading temporarily.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀

[MRJ86]

Hi Deenuji

I have not seen this error before, but the robots have not been running for a week beforehand, which updating the PAD version fixed. I dont know how to roll back versions of PAD, but the way I understand it, PAD robots are not backwards compatible and therefore my robots wont run in and old version of PAD now that I have updated.

I dont see how handling errors can be usefull here, is there issues with actions throwing errors in unattended mode, which stops the robots mid run and NOT reporting back to the parent Power Automate Cloud Flow? 

Best regards

Mikkel

[Deenuji]

@MRJ86 

If you haven't included any new version actions in the existing bots, downgrading to the previous version might negatively impact your existing bots.

Regarding error handling, yes I agree with your point. But you can utilize a log file to record periodic logs for actions, ensuring that all actions are executing as expected. Even in the event of a failure, you can review the log file on your local computer to diagnose any issues occurring during bot execution like below.

Thanks,
Deenuji Loganathan 👩‍💻
Automation Evangelist 🤖
Follow me on LinkedIn 👥

-------------------------------------------------------------------------------------------------------------
If I've helped solve your query, kindly mark my response as the solution ✔ and give it a thumbs up!👍 Your feedback supports future seekers 🚀