Hi Elexis, a couple notes about what I've seen. When the Timer kicks off on the Task to the Workflow, true enough, it appears that WF is grabbing the form data from the previous task last submitted on the path (which in this case is the starting form) and whatever the data values were at that time.

Thinking about this further though, there is another inherit problem even after overcoming that. The Workflow engine is not sequential but Multitasking and may run multiple WF's at the same time meaning that as they get their data from the form, each workflow instance may not get the last updated data from the other WF's from the form, but what was available when the workflow started which could be before the data was updated. As you are terminating the Task and started kicking off the WF from there, there is a possibility they could run together which would cause an undesired outcome.

I'll give it more thought and ping you if I get any ideas

Thanks Steve. I did realize that and plan to account for that by having cascading interrupt timer intervals. So I think I can account for that.

Hi Elexis, well having digging and playing with this some more, here is what I have for you. Because of the way Forms works you're going to have to change your logic a little bit, but not to much.

Explanation. By putting an Inclusive on the back of your parallel, it will wait for your User task to either complete or to be Interrupted before it can move forward. You must add the Workflow at each task so they can each exit to the Inclusive gateway otherwise if they grouped together at the WF Task the Exclusive gateway would only think it was waiting for 1 task and would allow that task to continue beyond the gateway before the others were completed.

In this way, you will know everyone voted or had their task interrupted as it will not continue past the gateway until that point.

For you decisions on the other side, your exclusive gateway can test the Total as the WF's increment the total as each task is completed, but does not run when interrupted. For your Exclusive task to see if a Majority voted or not, you can apply rules such as  ie: >3 then Majority, <4 then Not Majority, etc.

Hope this helps and my explanation makes sense

Oh good idea. I'll give this a try as well. Thanks!

I do still have an outlying issue. I am unable to access the current form variables with a WF started from an interrupted path. I have a support case on this to determine root cause, but the inclusive tip definitely helps!

Wait. This may mean I CAN terminate on the interrupt instead of trigger a workflow. Thanks I have some testing to do.

Yes, the Timers can/will Terminate the Approver Task

And you don't have to worry about that Forms variable support ticket to be resolved as it no longer applies here, I think :)