Hello,
I'm encountering what I believe is either a known (but not to me) limitation of the Power Automate Unattended RPA addon, or a possible configuration issue. However, I'm not sure which it is and every
MS Docs I've read doesn't seem to clarify my scenario.
I've done my best to explain my setup below and then the current issue I'm stuck on. Any ideas would be greatly appreciated.
- 2x - Shared User Account (Win 10 & O365 E5 Lic.)
- 2x - Power Automate RPA Attended Lic. Assigned
- 1x - Environment
- 1x - Power Automate RPA Unattended Lic. Assigned
- 1x - Microsoft Server 2019
After the recent removal of the Gateway requirement to run a desktop flow unattended, I'm now using cloud flows connecting directly to the desktop flows through an Environment to Machine connection. I've gotten this to work in one scenario but when I try to expand to my planned setup I'm stuck.
I've gotten this setup to work so far:
(Example below is only using the first Shared User Account)
- Shareduseracct01 running Power Automate Desktop on Win19 Server
- Shareduseracct01 has RPA Attended license assigned
- Created a desktop flow to send a test email
- Setup the Machine to Environment connection through Power Automate Desktop settings
- *Environment has Unattended RPA addon assigned
- Setup Power Automate scheduled Cloud Flow with the direct to Machine connection
- Uses Shareduseracct01 credentials
- Desktop Flow "Test01" selected
- Run Mode is set to Unattended
Everything in that setup works as it should with no issues. However, the issue comes in when I try to utilize the 2nd Shared User Account as well.
- Shareduseracct02 also logging in on Win2019 Server
- Shareduseracct02 has RPA Attended license assigned
- I created a desktop flow "Test02" so I can test scheduling two different Cloud Flows
- Each using their own Shared User Account, on our Win2019 Server
- Each running their own Desktop Flow with the Unattended run mode, at the same time
- Logged into Power Automate web portal with Shareduseracct01 and created a new scheduled Cloud Flow with the same connection type of direct to Machine.
The problem is that when I do this it shows the Machine connection but only shows the Desktop Flow I created using the Shareduseracct01. I thought it was the login credentials so I changed them in the flow to use the Shareduseracct02 login. Even with changing them, it still doesn't show the Desktop test flow created on the Shareduseracct02 account.
I thought it might be from not setting the Machine to Environment connection on Shareduseracct02's desktop app and set it up as I did on the 01 account. When I did this, the Cloud Flow (set with the 02 accounts credentials) showed me the Desktop test flow created on the 02 account. Perfect!... Unfortunately not. When I do this, the Desktop flow on the 01 account (even with those credentials tried) doesn't show up anymore. I realized also when I setup the Machine to Environment connection on the 02 account, it knocked the 01 account's Desktop to Machine connection offline.
From everything I've read, an Environment with an Unattended RPA addon assigned should be able to support running separate Cloud Flows, to trigger separate Desktop Flows, on their own shared logins that have the RPA Attended licenses assigned.
Everything that I've found on running unattended flows seems to imply that this should be possible with both shared logins as long as it's on a Server.
If anyone knows if this is a known limitation or if you have an idea of what I might have missed/setup wrong, I would greatly appreciate the info!
