Unanswered

Power Automate Unattended Runs Using Virtual Machine

(1) Share

Report

Posted on by ssacda

Has anyone experienced issues where certain "Click UI elements" or "Move Mouse to Image" (and send click) only fail during Unattended runs? Our machines have the configuration file to make sure the VM has the correct resolution. Below is an example of the most common errors we've seen.

Problem while executing action 'Click'. Click failed (error while clicking)

Microsoft.Flow.RPA.Desktop.Modules.SDK.Extended.Exceptions.InternalActionException: Click failed (error while clicking) ---> System.InvalidOperationException: Some simulated input commands were not sent successfully. The most common reason for this happening are the security features of Windows including User Interface Privacy Isolation (UIPI). Your application can only send commands to applications of the same or lower elevation. Similarly certain commands are restricted to Accessibility/UIAutomation applications. Refer to the project home page and the code samples for more information.

at WindowsInput.WindowsInputMessageDispatcher.DispatchInput(INPUT[] inputs) in...

Any help would be greatly appreciated. There error messages are not always the same, but the UI elements seem to be the same.

Categories:

General topics

I have the same question (0)

All responses (3)

Answers (0)

ManishSolanki 15,091 Super User 2025 Season 2 on at

Like (1)

Report

Hi @ssacda

It looks like default size of screen resolution is the issue for unattended run. You may try new feature "image as fallback" for UI selectors. I have recently published a blog to demonstrate this feature.

Set up fallback UI automation mechanism in PAD (manish-solanki.com)

Please refer the documentation for known issues & limitations:

Set fallback mechanism for UI elements - Power Automate | Microsoft Learn

OR

You can modify the default screen resolution for unattended runs using one of the methods mentioned in the below link:

Set screen resolution on unattended mode - Power Automate | Microsoft Learn

I hope this will help you in fixing the UI selector issue.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

Was this reply helpful? Yes No
ssacda 4 on at

Like (1)

Report

Hi @ManishSolanki ,

I did something similar, but I wonder if the Image fallback works different? What I did was upon error for the UI or image, I told it to run a sub flow which would do the opposite (If UI, click image - if Image, click UI), kind of like the image fallback. Would the fallback function differently? We also have a job that edits our config file to say True to the resolution and we verified that it does in fact say true with the correct resolution.

Do you know where we might have a discrepancy since the error seems to be resolution related but our config file says its correct?

Thank you so much for your help!

Was this reply helpful? Yes No
ManishSolanki 15,091 Super User 2025 Season 2 on at

Like (1)

Report

Hi @ssacda

Pls check the screen resolution size in log file when run in attended mode. Try to run unattended mode with same screen resolution. You may use set resolution action to modify default value in unattended mode but that requires admin privileges for RDC account, or you can set the default screen resolution for unattended run using the method mentioned in my previous reply.

If this helps & solves your problem, please remember to give a 👍 and accept my solution as it will help others in the future.

Was this reply helpful? Yes No