We have a workflow process with InfoPath integration, thus sending users InfoPath Client Events.

Users log into SharePoint, navigate to the specific site and library, click on the New button and open the first
view of the infopath form. They complete and submit the form which starts the workflow process.

When they open their first task in SharePoint from the K2 Worklist Web Part, and decide to close it again,
K2 creates a copy of the form and first view (or task) and place it in the root of the library in SharePoint.

Users then access this task again later either using the K2 Worklist Web Part again or by directly opening the
InfoPath task previously copied to the library by K2. The task is then filled in by the user, completed and
submitted.

Note: All tasks are configured with a Save (update) and Complete action, as was requested.

When the users complete the first task, it is not always removed again from the library by K2, but stays
behind. Why is this happening? We tested a bit, creating a few process instances, where we noticed
that the tasks were removed in the library most of the time, but not always. Guidance and help appreciated.

It is well known that K2 does copy the InfoPath task to th root of the library when selecting an update action, which meakes perfect sense because it needs to be stored somewhere for use later. And after the task is then completed at some point, K2 then removes the task from the library root.

Is this setup/deployment and config normal for InfoPath integrated workflows in SharePoint? Should this be approached differently or is this a known problem?