Hi, one user is experiencing troubles with tasks completion. When he completes j

Can you check in the process model, if there is a node which has been configured as MNI? If yes, can you make sure all the instances of that node finishes at once instead of one at a time? You can also check, how many instances of task have been completed when task is submitted? If only one task instance is completed, you can eliminate browser or any other form behavior from the issues.

thanks for the answer. No MNI is not configured in the nodes, it is various nodes in different process models - all used by a lot of users who do not face the issue, except one. It is visible in the history that the instance get duplicated after completion (attached process history example)

Can you post a screenshot of the process monitor corresponding with that history snippet?

Attached the nodes overview of the history example and the two nodes details. You can see that the "Sales Approve final TS" task has been duplicated a first time at 17:31, the user received it again twice (it's an approval task), he has submitted again the two tasks at 18:10 and each of them were duplicated (leading to 4 duplicated flows)

And just for thoroughness, is there anything special about (/can you share) the assignment properties for the user input task?

Nothing special, it is assigned to the Sales user team ("salesDepartment" process variable generated by a script based on the Sales user)

Can the issue be reproduced if the user in question is assigned any tasks individually?

@olivierd Hi, I suspect that there could be some configuration made in the 'Scheduling' or 'Other' tabs. If possible, could you please post the images of the 'Scheduling' and 'Other' tabs as well?

In addition to the above, is there is a possibility of the chance of re-execution of this node? If so, please make sure that 'Do not create if active instances exist' or 'Delete previous instances that are still active.' ('Other' tab >> 'Execution Options' >> 'When this node is re-executed:') is checked.

I further suspect that there could be a node (some where before the user input task) which is spawned. If this is the case, make sure that 'All instances are done' ('Other' tab >> 'Multiple Instances' >> 'Run all instances at the same time') is checked.

* If this is the case, make sure that 'All instances are done' ('Other' tab >> 'Multiple Instances' >> 'Run all instances at the same time' >> 'Move on when:
') is selected, if 'Run all instances at the same time' is checked for spawned node.

@mschmitt : it looks like when a task is assigned to the user only it is not duplicated, but it might just be "lucky cases" so we will test it several time and confirm.
@sikhivahans: the print screens are attached, yes there is a possible re-execution. I don't think it is due to a configuration of the nodes or the previous ones as this issue is only occurring for one single user (the node with the example above are heavily used by many users w/o any issue). I guess changing the mentioned configurations might just fix the duplicated task, not the root causes - plus we would have to apply that in all possible nodes that the concerned users might execute... I have tried in the past to check " Do not create if active instances exist." and the issue was still occurring.