Instant flow in business process flow not showing status for users

(0) Share

Report

Posted on by Svenny

153

Hello,

I am trying to share a business process flow containing several power automate instant flows to users. They can trigger the process, but the status of the flow run will not show for them.

I am suspecting this might be a some permission the users are missing, but I don't know which ones. It is working for me as the owner and creator of the solution.

Am I on the right track here? Do anyone know which permissions are required for a user to successfully run a instant flow within a business process flow?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (9)

Answers (1)

Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (0)

Report

Hello @Svenny

Make Sure the Respective user have proper security role. User who is triggering the flow show have access to the Respective entities(Which is available in the Flow).

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Svenny 153 on at

Like (0)

Report

Thank you for your reply @rampprakash

The users have access to the tables / entities being used within the flow and business process flow. Here, they have been added as run only users. A security role has been created where the users have been granted the appropriate permission to the 4 tables used in this business process flow and related instant flows.

However, the status of the flow itself is still not visible to them. I suspect they may be missing permissions on the table / entity where Power Automate stores the status for each flow? But I am unsure what this table / entity is called.

Could that be this issue? If they don't have read permission to the table showing the status of flows, they would not be able to view the latest status of the flow run? Running, successful, failed, cancelled etc. This status does not show for them, but turns out blank. From the users perspective, it appears the flow has never been run.

However, they are able to trigger it, and I see in the logs that they run successful without any issues in the flows themselves as expected.

Was this reply helpful? Yes No
Kessi 11 on at

Like (0)

Report

I am having the same issue. The user cannot see the status of the instant flow which is part of the BPF. This is preventing the user to advance in the BPF as this flow is required.

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like (1)

Report

This may or may not help Identify Missing Permissions in Dynamics 365 CRM | Microsoft Dynamics 365 CRM Tips and Tricks (inogic.com) but it will show you how to use browser developer tools to potentially capture the messing permissions - depending on where the error is generated they may or may not show up as errors in the browser console log..

Was this reply helpful? Yes No
Kessi 11 on at

Like (0)

Report

Hi @ben-thompson ,

Thanks for this! This is very useful for future purposes.

I have worked around the problem by importing the Minimum App Use Priveledge security roles that microsoft provides, which somehow solved the problem.

Cheers

Was this reply helpful? Yes No
Ben Thompson 1,400 on at

Like (0)

Report

That can't have fixed the problem by itself - I assume you installed the Minimum App Use Privilege role and gave that role to the appropriate user?

If that did fix it you should give that role to all users going forward as otherwise the problem will re-occur. And if you didn't give the role to the user then the issue is definitely elsewhere.

Was this reply helpful? Yes No
Verified answer

KrzysztofNk 11 on at

Like (2)

Report

Hi, I have found this https://github.com/MicrosoftDocs/power-automate-docs/issues/746. According to this you need to add Read privilege on SystemJob in Customization. In my case adding read privilege on Organization level works perfectly fine

Was this reply helpful? Yes No
Kessi 11 on at

Like (0)

Report

Hi KrzysztofNk,

Thank you for the advice! I think this is what I needed. Works now.

Was this reply helpful? Yes No
Svenny 153 on at

Like (0)

Report

@KrzysztofNk

Thanks for replying with the solution.

I spent some time with Microsoft support on this issue, and adding the SystemJob privilege was the solution.

We also tried some other privlileges which seems to have been redundant with the information available in the github issue you linked to.

Was this reply helpful? Yes No