Unanswered

Flows are not visible for users who sign in with their personal accounts

(17) Share

Report

Posted on by kostasc Microsoft Employee

Hello Power Automate Community,

We wanted to inform you about an issue affecting users who sign in to Power Automate for desktop using their personal Microsoft account. This issue prevents affected users from viewing their flows in the console. Please note that this issue does not impact users who sign in with a work or school account.

Our team is actively working on a solution and we will provide updates as soon as possible. We appreciate your understanding and patience as we resolve this matter.

Update:

We have successfully resolved the issue, and a new version of Power Automate for desktop is now available in the Microsoft Store. This update addresses the problem and ensures that affected users can once again view their flows in the console. For those using the portal version of Power Automate for desktop, you can download the updated version using this link.

Best regards,
The Power Automate Team

Categories:

Power Automate Desktop

I have the same question (0)

All responses (43)

Answers (1)

trice602 15,331 Super User 2025 Season 2 on at

Like (3)

Report

Flows are not visible for users who sign in with their personal accounts

Thank you for sharing! Great to see proactive acknowledgement and communication. 100%

------------------------------------------------

⭐ If this was helpful, please like and/or mark as a verified answer to help others find this too!

Always glad to help! 💯💯💯💯💯

Tom

Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn

Was this reply helpful? Yes No
CU20112353-0 2 on at

Like (1)

Report

Flows are not visible for users who sign in with their personal accounts

Disaster. Could not work without it. Need you.

Was this reply helpful? Yes No
CU21110132-0 3 on at

Like (2)

Report

Flows are not visible for users who sign in with their personal accounts

Thank you for the notice.

Let me share my research.
I found the mismatch of cTag between JSON in HTTPS response and meta-file in the below folder.

C:\Users\user-name\OneDrive\Apps\Power Automate Desktop For Windows

It may be the main cause of this issue.
Recently, it seems that the cTag in HTTPS response are totally changed like the below.
cTag="c:{*********************************},2" etc.

Currently I changed the cTag in each meta-files to match with response's, one by one, for my urgent recovery.
But it'll be difficult for the ordinaly users.

I hope this info will be helpful for your team, and you'll find the good solution.

Best Regards,

Was this reply helpful? Yes No
CU21110744-0 3 on at

Like (1)

Report

Flows are not visible for users who sign in with their personal accounts

Thought it was just me, happy to see a notice in the app itself. Not sure if it's also worth mentioning but whenever signing in with my personal account it keeps on asking my login details for about 5x. Hoping to see a solution soon as I need this on my daily work!

Was this reply helpful? Yes No
Verified answer

kostasc Microsoft Employee on at

Like (3)

Report

Flows are not visible for users who sign in with their personal accounts

Hello Power Automate community,

We have an important update regarding the issue affecting users who sign in to Power Automate for desktop using their personal Microsoft account. We are pleased to inform you that a fix for this issue will be released tomorrow in the Microsoft Store version of Power Automate for desktop. The fix for the portal version will be applied shortly after.

We appreciate your patience and understanding as we are working to resolve this matter.

The Power Automate Team

Was this reply helpful? Yes No
CU21111401-0 5 on at

Like (0)

Report

Flows are not visible for users who sign in with their personal accounts

Dear Power Automate Team,

Thank you, this is really good news!

Was this reply helpful? Yes No
pushkraj 3 on at

Like (0)

Report

Flows are not visible for users who sign in with their personal accounts

Thank you for the update, Power Automate Team.

For those encountering this issue, I understand how critical it can be to maintain productivity. While waiting for the official fix, I recommend exploring potential workarounds shared in the community and related forums. I got it working by making some changes.

Appreciate the hard work the team is putting into resolving this!

Pushkraj

LinkedIn - Pushkraj Jori, Software Engineer | LinkedIn

Was this reply helpful? Yes No
Suggested answer

angelosa on at

Like (2)

Report

Flows are not visible for users who sign in with their personal accounts

We are excited to share some good news regarding the recent issue affecting users who sign in to Power Automate for desktop using their personal Microsoft accounts.

We have successfully resolved the issue, and a new version of Power Automate for desktop is now available in the Microsoft Store. This update addresses the problem and ensures that affected users can once again view their flows in the console.

For those using the portal version of Power Automate for desktop, you can download the updated version using this link.

We appreciate your patience and understanding as we worked to resolve this matter.

The Power Automate Team

Was this reply helpful? Yes No
CU12100917-0 6 on at

Like (1)

Report

[Resolved] Flows are not visible for users who sign in with their personal accounts

In my hotmail account environment, even after installing the latest Power Automate for desktop(https://go.microsoft.com/fwlink/?linkid=2297775), the flows I created in the past are still not visible.

I believe that when the Graph1 folder was created, I might have manually copied data from the Graph folder, which could be the cause of this issue. Please let me know if there is a solution for this.

Was this reply helpful? Yes No
CU21111401-0 5 on at

Like (0)

Report

[Resolved] Flows are not visible for users who sign in with their personal accounts

I run PAD from personal account on my desktop PC. I have downloaded the new PAD version via the link that was shared to us and can confirm the fix is working - all of my desktop flows are now visible again. Thank you very much Microsoft PAD team!

Was this reply helpful? Yes No