Wait For Everyone to Approve Condition Not Working Consistently

[Alan42]

We have a new employee setup request workflow that is behaving oddly.  Both the HR representative and manager selected on the form should approve the RITM before any tasks generate.    The 'Wait For Everyone to Approve' condition is selected.    We had two almost identical requests placed in the past day.  Both were submitted by and for  the manager.   The first generated tasks when the HR manager did their approval although it is still awaiting manager approval.   The second was approved by the HR rep and is awaiting manager approval.  The second has, correctly, not generated any tasks.  All the approvers belong to the same groups and have the business_stakeholder role.     Any idea what we need to change to make the behavior consistent?     

[Brad Bowman · Accepted solution]

Your approval activity looks fine, except for ensuring the value you push to the answer array is a string.  sys_ids can cause unexpected results if not forced to a string, so use:

answer.push(current.variables.employees_manager.toString());
answer.push(current.variables.hr_representative.toString());

If you can re-create the issue after this change with the same users and test case, look at the executing workflow to see if the approval activity shows completed, and if you hover over the activity if it shows anything helpful.  In this case, is there still an approval record in the requested state, or is there something going on with that other user - the variable didn't get populated, the user is not active,...?