-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are times when flows running in the Power Platform Admin View are not running properly (e.g. Admin | Sync Template v4 (Flows)). #9379
Comments
Can you please confirm that the user identity installing and running the flow has the Power Platform Admin Role assigned both directly and permanently? |
OK unfortunately I'm not sure how to help. Your PPAdmin Role needs to be assigned permanently. Here is how to set PPAdmin Role as direct and permanent. |
I'm afraid you'll need to reach out to product support to find why you cannot see or set to permanent access here. The reason access needs to be permanent is that the kit runs its flows at unpredictable times so the identity running the flows needs access at all times Ex: |
I see, thank you very much. |
I look forward to hearing what this mystery might be of the missing end-time configuration. |
Hello. |
Have you checked this message? |
Hello sorry we've been on holiday over here. #9447 The way to test this will be to see if your permissions are recognized in the flows. So note a flow that gets marked deleted, note its envt and flow GUIDs. Are the flows which were marked deleted returned in the call to List Flows as Admin? Do they make it through the filter? |
I see you were on vacation, my apologies. |
That means you have 450 active environments. I apologize for the inconvenience, this is the only way to catch the repro without you being actively creating it. If you actively create it then we know you have permissions at the time. |
closing out as no further action for starter kit team |
Does this bug already exist in our backlog?
Describe the issue
We are currently using Admin | Sync Template v4 (Flows) to count the number of PowerAutomate flows in our environment on a weekly, date/time basis. In one of these cases, about once a month, a flow that was actually still in use was treated as deleted. We then discovered that the timing of the deletion of the flows that were flagged for deletion coincided with the time that Admin | Sync Template v4 (Flows) was unnaturally stopped.
The above image shows the execution history of Admin | Sync Template v4 (Flows). 12:21 to12:38 on 12/8 is unnaturally vacant. This flow runs every day, and the execution time on this day was 11:02 to12:48, which is about 2 hours every day, and the flow has been running almost every minute during this time.
The screenshots of the two Excel sheets above show those flagged for deletion on 12/8 in order of the time they were flagged. The top image shows the start time and the bottom image shows the end time, which falls between 12:21 and 12:48 when Admin | Sync Template v4 (Flows) was stopped. The deletion appears to have been automatic, as several items in the same environment were deleted at exactly the same time. In addition, 120 of these were deleted, most of which are flows that were not actually deleted.
We would appreciate an investigation into the cause of the occasional stoppage of the above flow, and if possible, an improvement in the flow.
Expected Behavior
This flow (Admin | Sync Template v4 (Flows)) will continue to run daily without interruption. It does not flag non-deleted flows for deletion.
What solution are you experiencing the issue with?
Core
What solution version are you using?
4.43
What app or flow are you having the issue with?
Power Platform Admin View
What method are you using to get inventory and telemetry?
Cloud flows
Steps To Reproduce
The following is done when the flow is found to be unnaturally reduced.
Anything else?
Flows that run per environment over the same span of time, such as Admin | Sync Template v4 (Apps) and Admin | Sync Template v4 (Custom Connectors), also saw outages during the same time period.
This suggests that the problem is not limited to Admin | Sync Template v4 (Flows).
The text was updated successfully, but these errors were encountered: