Like it says in the title, I got a flow on flow designer that is using an approval action to create multiple approvals, the conditions for approval and rejection on this flow are the following.
For approval condition is set so it should wait until everyone has responded and approve if there is at least one approval from the users.
This one is working properly.
For rejection condition is set so everyone rejects, so this one should only trigger in the case that every user asked for approval has rejected.
The problem here is, that once there is any rejection of the group of users this makes the rest of the approvals be set to "No longer required"
I have scoured through the platform believing a Business Rule was causing the issue but I cannot find any that could be causing this behavior, is there any other element that could be interfering or causing this? Is this a known issue of the Tokio release?
The flow is targeting a catalog item at the moment and its getting the users that should be approved from a variable in it, so the amount of users that have to approve changes according to this it could be 1 or as high as 6 users.
