OK so I tested this with 3 approvers - 1 approves and is fine waiting on others. Once the 2nd approver replies approve or reject, it cancels the workflow and states "The task is no longer active. Another user may have already completed the task." I've attached a screenshot of the workflow with flexi task for 3 approvers.
Hmm, why does FlexiTask 2 look different from the other two tasks? Are its branches further down? I've not seen that in 365 (we just have "assign a task" action and the workflow just widens to show all ).
Ahh, I don't think I have that magic in 365 either! In any case, are you able to see the tasks in a task list and verify that a separate one is created per flexi task assignment? Can you log the IDs of the created tasks to verify that separate ones are created? Also, it may help to have a pause for every other creation possibly?
And for grins, I tried with another approver other than me and workflow still cancelled on 2nd and 3rd approvers that were still outstanding! :(
Hmm, why not use this action: Assign To-Do Task
This part of that config is particularly interesting:
Create individual tasks for all group members
In the case when a group is assigned the task and Create individual tasks for all group members checkbox is:
- not selected, all users in that group will receive the task notification. The first respondent will represent the entire group.
- selected, an individual task will be assigned to every member of the group.
Thanks Brian!! Very detailed and informative!! On your parallel flexi tasks, are yours not cancelling the others out when another branch replies as that's what happened with mine. First approver went thru fine but once the second one replied with lazy approval it errored out and cancelled all the other tasks! :( I'm now doing individual workflows for the 12 approvers.