You’re offline. This is a read only version of the page.
12
Hi,
I have set up a custom response with "Wait for all responses", and a condition of "does not contain Reject". This approval works with 3 or 4 users but once it gets to around 6 or 7 users even after everyone has responded the approval just sits and waits and then cancels itself after 30days.
I found the following in Microsoft help "Approvals that rely on custom responses can fail if they're sent to many users with the type set to "Everyone must approve". This failure is due to data size limitations of the results field."
Does anyone know when the issue will be rectified or if there is a current workaround? I have used parallel flows before but this is a hefty workaround with multiple users.
Just create an array of approvers and loop through them. The array could be a SharePoint person or group column that allows for multiple entries. The bottom line is that you can dynamically create an array - no need to edit the Flow for different approvers.
Hi Scott,
Thanks for your reply. I run these approvals regularly with different approvers, would your suggestion be easy to edit or would this require addition/deletion of strings each time.
Trying to keep the workload to be as simple as possible
Thanks
As a work around, consider assigning individual approval actions in a loop to each approver and turn on concurrency for the loop. Use a string variable and append the response of each approver to the variable.
After all of the approvals complete, evaluate the string for a response that means the item was rejected and take action as appropriate.
Alternatively, if any of the approval actions have a "rejected" response, take action as appropriate and then add a control terminate action (with success). This will stop the Flow.
#1
WarrenBelz
146,660
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,004
Most Valuable Professional
Share
Report
All responses (
Answers (
