Phew..! I took about 10 minutes to think of how to put the question. Well, the scenario am facing is pretty weird and unexpected and it has left me no choice but to put this here on Nintex Community. And I will try my best to explain the situation I am stuck at.
Okay so, below is a look of a part of my workflow where this problem is being occurred
As you can see in above image, I have a parallel action with three branches. Each branch have a state machine with two flexi tasks in it. The flexi tasks named as Owner1, Owner2 and Owner3 are the original approver tasks and are run only one time, while the tasks named as Reassigned owner1, Reassigned owner2 and Reassigned owner3 can run multiple times.
see image below,
When the workflow is initiated, it goes to a task for Managers approval and Manager can assign task to Owner1, Owner2 or Owner3 or all of them.
Lets Suppose, I am Manager and I assigned task to Owner1 and Owner2.
So far, it works fine.
Now both the Owners, Owner1 and Owner2 will assign task to a user named (Training23).
Note: Training2 have display name as Training23
What happens next is where I am very confused.
Look image below,
And following the same way, I tried to reassign Training23 from both Reassign Owner1 and Reassign Owner2. (Note: we are now on Reassigned State)
This happened every time I tried to assign task to a certain user from both Reassigned Owners 1 and 2.
I hope I have made my scenario cleared enough.
if any queries regarding my question, please feel free to ask.
I need help to get out of this situation as soon as possible (its urgent though).
I really am very confused by this.
Are you saying that you delegate a task to a user (training2) but it assigns to another user (training3).
Does it happen on all of them like that?
I've never had a need to built a workflow with several parallel state machines. and I do not even can imagine a process that would need anything like that.
but from other posts on the forum I have a feeling having parallel/several SMs within single workflow or even parallel task actions is not very reliable.
for your scenario, I would suggest to move handling within parallel branches into a separate workflow(s).
from you screenshot I believe you would be able handle it with a single workflow since there seems to be no difference among 3 SMs. just different owners.
that would significantly simplify things for you.
so at the end you would have a parallel action that would start separate instance of the same (site) workflow, one for each designated owner.