Hello All,
I have a flow that runs daily and pulls in data using SQL power query from Purchase Order data table. Using this data, it will roll into an approval step that will then send out emails based on Teams approval response by a buyer in our procurement group. With each row of SQL data corresponding to an individual Purchase Order, there is an "Apply to Each" function built in here with the concurrency control set to maximum (degree of parallelism = 50).
My fear here is if the Teams approval goes unanswered, the flows are in a "pending" state. As I understand it, the flow can retain 50 of these using the concurrency control. Firstly, what happens if you exceed this limit? Does the flow break or will it cancel the flows based on age? If it does halt the older forgotten flows, I may be all set.
If not, can I utilize the flow duration setting to essentially "self-clean" the flow and keep well inside the 50 flow limit? For example, if I have 5 flows a day and these are not addressed at the approval step, in 10 days this will add up to the 50 parallel flow limit as the default duration to hold this step is 30-days. If I can reduce this limit to 5 days, it will toss out the older runs and keep the approval running each day.
The flow was originally designed to be addressed by the respective buyers each day and I've tried to send reminders to keep their approval queues clear but human nature is what it is and sometimes these just start to pile up. If they could "age out" after 5 or so days, it is no issue for the buyer as they have probably already moved onto something else.
