Power Platform Community Forum Thread Details

Looping Flow Issue

Hi all

I've created a flow that I'm getting warning for -

Your flow is running too many actions

Your flow has used more than 80% of its Power Platform Requests (https://aka.ms/pa-ppr) limit in the past 24 hours. The performance is currently not impacted as it is below limits. But if the usage grows, further actions may be throttled or slowed down. Power Platform Requests used: 8742, Power Platform Requests transition limit: 10000.

Flow name: Action Tracker - Closed Status adds date

The flow is linked to an Action Tracker. What I'm trying to achieve is that when an action is raised the Action Status is 'Not Started'. It may be changed to 'In Progress' during the course of the action being dealt with, but when it ready to be closed the action assignee completed details of what they have done to close the action, then changes the Action Status to 'Closed'. At this point I want the day of closing (i.e. todays date) to be automatically added to the Closure Date field for that specific action. The Closure Date field is hidden from form and edit view so people can't add in a date previous to the target date, so in effect to eliminate cheating.

I have this working, however I am getting the above warning, plus a warning when I save that it will result in an infinite trigger loop, which I assume is why I'm getting the email warning. Also, checking the action tracker list daily, each day the Closure Date is changing to the current date, when I need it to stay fixed at the actual day it was closed.

Below is current set up

Trigger - When an item is created on modified

Condition

If Yes

Thanks

Darren

Categories:

Business Process Flows

You do not show your entire flow, so I am not positive of your issue. What is your flow trigger? Is it when an item is created or modified? If so, should this flow only run when the action status is equal to Closed and the Closure Date is null? If so, delete the condition in your flow and add trigger conditions instead. You will need to add two trigger conditions:

Action Status eq Closed: @equals(triggerOutputs()?['body/ActionStatus/Value'], 'Closed')
Closure Date is empty: @empty(triggerOutputs()?['body/ClosureDate'])

With trigger conditions, all conditions must evaluate to true for the flow to run. You can read more about trigger conditions at Power Automate Trigger Conditions made EASY.

From what you describe, when your flow runs and you update the item with the closure date, it triggers the flow to run again. When it runs again, it does the same thing this causing the infinite loop warning you get.

Quick Links