Using Parallel Approvals in Flow Designer is only respecting the Approval Decision of the First Approval - Known Error

Using Parallel Approvals in Flow Designer is only respecting the Approval Decision of the First Approval Description When using Multiple "Ask For Approval" Actions inside a "Do the following in parallel" Flow Logic you are seeing that the Decision from the First Approval is being applied to all of the Approvals .

Example:

There is 2 Group Approvals inside the Parallel Section of the Flow When one User approves for Group A it is approving the "Ask For Approval" Actions for BOTH Group A and Group B Steps to Reproduce

Create a Flow 2. Set the Trigger to Service Catalog 3. Add a "Do the following in parallel" Logic Step 4. Add 2 "Ask For Approval" Actions to run in Parallel 5. Set the Approvals to different Groups 6. Set When to Approve to 'Anyone approves' for each Approval Action 7. Use "Test" on the Flow and select a Request Item 8. Go to the Request Item and Approve one of the Approvals 9. See that all Approvals get set to "No Longer Required" 10. Check the Flow Context and see that both Approvals are set to "Approved" Workaround Remove the value in Approval Field on the Ask for Approval action in your flow. Emptying this field has 2 effects:

The Approval Field field on the table might no longer be updated with the result of the Approval record. If this is required for your further process, make sure to add an Update Record action later in your flow. The action will no longer create a record watcher for the state of approvals related to the task. For several approval actions in parallel branches, these record watchers lead to marking the other approvals as "No longer required" once the first approval has been completed. If there are no record watchers, each branch will wait for the completion of the approval in that branch, regardless of any parallel approvals.