Two consecutive Ask for approval, Second Ask for Approval going to "no longer required" - Known Error

Two consecutive Ask for approval, Second Ask for Approval going to "no longer required" Description When you have 2 consecutive executions of Ask for approval action in a flow/subflow such as within For Each flow logic for example, the approvals generated by second execution of Ask for approval action could be set to "No longer required" intermittently.

If the time difference between the started time of each "Ask For Approval" action execution could be just few seconds, then there is a possibility of a race condition/timing issue here because there are consecutive executions of "Ask For Approval" action for same record within just few seconds time. Therefore, as approvals generated by first execution of Ask for approval action are still being approved or rejected, there is a chance that the approvals generated by second execution of Ask for approval action could be set to "No longer required" intermittently.

Steps to Reproduce

Make sure you have multi node system 1. Import attached update set 2. create incident with short_description = approval, this will trigger flow 3. open sysapproval_approver.list on node1 and node2 4. Approve one record for incident on node1 and second for node2. Actual Flow reach to COMPLETE Expected Flow should remain on second Ask for approval

Workaround Add a "Wait for a duration of time" flow logic with a duration of about 30 seconds right after any "Ask for Approval" action in order to decrease the possibility of a race condition/timing issue. Please note that 30 seconds duration is just a guideline/suggestion. You could set the duration based on average execution time of each Ask for approval action execution.