Hi,
We have a flow being activated from a Power Apps button that does a couple of data operations and then executes a desktop flow (attended). Devs and end users were able to execute the flow in both the dev and prod environments until Wednesday morning (the day after deployment). The only thing that changed in the deployment for this flow was the target machine for the desktop flow. We ran into a couple of errors in the deployment process (unrelated to the execution of this flow), but by the time Wednesday rolled around, we were running into this issue.
Users should be properly licensed, we've given a varying degree of licenses to various users: our service account, one end user, and I have every license that we have available to us assigned to them (premium, per-user, free), and another dev and the other end users have only a per-user plan. Power Platform Admin Center returns no issues with licensing/capacity. Both me and the other dev are able to execute the flow as expected. Connections to the flow are set to use the ones we provide. We followed the same process we've done for all other flows in this app, but this is the only one that has issues.
So, the question is: did Microsoft just change its mind on us being able to execute flows overnight or is this an oversight on our side? And if so, what does remediation look like?
Any suggestions or input would be greatly appreciated, and if you need any other details, don't hesitate to ask. Thanks in advance!
Full error message:
X.Run failed: {"error":{"code":"0x80048d06","message":"{\"errorCode\":\"ConsumptionViolation\",\"message\":\"Flow 'X' cannot be activated because a Per-user plan with Attended RPA license is required to enable this flow.\",\"correlationId\":\"X"}"}}
