Unanswered

Desktop flow execution error - "WindowsIdentityIncorrect"

(0) Share

Report

Posted on by KLHOILDMSRPASVC

As I've developed multiple cloud flows recurring in a quite frequent manner, which all of them are executing desktop flows to read mailboxes registered in the MS Outlook locally.

Process A - recurring every 90 seconds

Process B - recurring every 90 seconds

Process C - recurring every 300 seconds ( 5 minutes )

Process D, E & F - recurring every 600 seconds ( 10 minutes )

I am recently facing a problem of the failure running those desktop flows through cloud flows, logging the error "WindowsIdentityIncorrect". The problem seems occurred in a quite random interval that sometimes the error would kept happening for an hour then resumed normal later on.

And I was failed remoting into the server during those periods as well. So I am not sure if this to be related to some Windows implicit setting of maximum login attempt(s) or not as my flows were scheduled to run with a quite high frequency.

Categories:

Power Automate Desktop

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

You may have a limitation on the machine as to how frequently you can login. But this usually kicks in on failed attempts. So it might be that it's not Windows causing the problem, but the problem (whatever it is) causing Windows to automatically lock the account. Not quite certain.

I have seen this error in the past and it would usually be related to MS services being down temporarily, and thus causing flows to fail. In some cases, this had broken the Desktop Flows connection in the cloud and a new connection needed to be created. In other cases the issue would disappear on its own. But both of these are actually quite rare.

It might also be that your security policy is causing this as well, where you sign in too frequently. Is there a reason for running your flows this frequently?

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.

Was this reply helpful? Yes No
KLHOILDMSRPASVC 4 on at

Like (0)

Report
Copy link

Link copied!

Thank you on your reply.

From your words, seems the failure of "WindowsIdentityIncorrect" could be coming from either the MS service down or the frequent sign-in ( the frequent flows' run )

Regarding on the MS service down in temporary, could this be a bug on the Power Automate?

Besides, on the frequency of the flows' run, I did set them up generally following the scheduling used in WinAutomation previously. Understanding the high frequency of flows' run hence login attmepts could lead into conditions, I can then rearrange the flow.

Was this reply helpful? Yes No
Agnius Bartninkas Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

WinAutomation did not have the limitations in place for how many flow runs you have. Also, it was running everything locally, so flows actually started more quickly. Power Automate uses APIs to initiate a flow run from the cloud and run it on the machine. There are certain limitations to that (how many and how frequently you can run them), as well as it is slower, so you will simply not be able to run those flows as frequently, if they take time.

Also, PAD only allows running a single flow at a time on a machine (no concurrent flow runs on a single machine), unlike WinAutomation. So, again, if you expect several flows to be able to run at the same time - that's not possible, unless you add additional machines (or additional user sessions on a Windows Server machine that supports multi-user sessions).

As to MS services being down - it's not a bug related to PA itself. It's just Microsoft experiencing issues with their servers that PA relies on. This can happen, but it is rare. I think I've only seen that happen like 2 or 3 times at most in the entire 2023.

-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.

I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.

Was this reply helpful? Yes No