Power Platform Community Forum Thread Details

In my code there is web browser automation which works fine at the beginning(in unattended mode), but after few clicks it throws an error. It's weird because on the same machine(Azure VM) it works fine in debugging mode, it works also whenever I press Play in application, it works also fine when it is being invoked from Power Automate Cloud flow in attended mode. But whenever I invoke it from Power Automate Cloud in unattended mode then it throws an exception. I think it's not related to selector, otherwise it wouldn't work at all. But does any one have any idea of what could it be? Why it works on all sorts of mode except unattended?

It's worth pointing out it's not first step in the process which failed. First few clicks work.

I can just add that this exact step is about pressing button on webpage, error message is in polish but generally it says that pressing button failed.

Categories:

Power Automate Desktop

The first step in debugging these sorts of issues is adding a Take screenshot action to your flow. If the flow throws an exception on the same step all the time, you can add the action right before the step that fails. If the step that fails is not static, you might need to add a separate sub-flow that takes a screenshot and then encapsulate your existing flow into an On block error block that will call the sub-flow on error.

Once you have that in place, run the flow in unattended mode to see what happens. When it throws an exception, check the screenshot it took to see what the screen looked like at the time of the exception. Perhaps there were some issues with the screen resolution, or maybe the page did not load properly. There might be various reasons why this could happen, but you won't really know until you see what the screen looks like at that point.

Try this and let us know what you see in the screenshot.