Hi All,

After successfully migrating all instances of all processes of an application to a new snapshot, we cannot delete the old snapshot, because we get this error:

CWLLG3256I: The 'Dokumentum feldolgozás' task with the 'Task.33245' identifier is assigned to the 'TDM WF Admins_S_3b73bfc5-f165-4a91-9c9d-ae630f366e55.1a346c18-a1f6-4200-9fe6-aa9c6c0001ee' managers group with the 'UserGroup.12128' identifier. The task is in the 'Received' state. The task is part of the '9328 - Dokumentum szignálás' process instance with the 'BPDInstance.9328' identifier that is in the 'Active' state.
Explanation: The task is assigned to a managers group for the snapshot that you want to delete. The snapshot cannot be deleted before this reference is removed.
Action: Before retrying to delete the snapshot, reassign the task to a group in a different snapshot using the "Assign Task To Group" REST API or ensure that the task has completed and then delete it using the BPMTasksCleanup command.

We don't understand this, because - we suppose - the migration must migrate everything. How can it happen that a team assigned to a task migrated to the new snapshot references to a manager team which is in the old snapshot (if we understand well the cause of the error)? Its crazy...

Now we decided to wait until all the migrated tasks will be closed, and we will delete the old snapshot only after that, but we want understand what's behind this phenomenon. Or if anybody can help us to free up the old snapshot, we could delete the old snapshot earlier.

So, what's behind this and how to avoid in the future or solve these errors?

Thanks,

Dear Laszlo,

As my team is facing the same issue, I would like to ask you if and how you managed to resolved this issue? Did you wait until the completion of all the migrated instances or you did find another way?

Hi All,

After successfully migrating all instances of all processes of an application to a new snapshot, we cannot delete the old snapshot, because we get this error:

CWLLG3256I: The 'Dokumentum feldolgozás' task with the 'Task.33245' identifier is assigned to the 'TDM WF Admins_S_3b73bfc5-f165-4a91-9c9d-ae630f366e55.1a346c18-a1f6-4200-9fe6-aa9c6c0001ee' managers group with the 'UserGroup.12128' identifier. The task is in the 'Received' state. The task is part of the '9328 - Dokumentum szignálás' process instance with the 'BPDInstance.9328' identifier that is in the 'Active' state.
Explanation: The task is assigned to a managers group for the snapshot that you want to delete. The snapshot cannot be deleted before this reference is removed.
Action: Before retrying to delete the snapshot, reassign the task to a group in a different snapshot using the "Assign Task To Group" REST API or ensure that the task has completed and then delete it using the BPMTasksCleanup command.

We don't understand this, because - we suppose - the migration must migrate everything. How can it happen that a team assigned to a task migrated to the new snapshot references to a manager team which is in the old snapshot (if we understand well the cause of the error)? Its crazy...

Now we decided to wait until all the migrated tasks will be closed, and we will delete the old snapshot only after that, but we want understand what's behind this phenomenon. Or if anybody can help us to free up the old snapshot, we could delete the old snapshot earlier.

So, what's behind this and how to avoid in the future or solve these errors?

Thanks,

Hi All,

After successfully migrating all instances of all processes of an application to a new snapshot, we cannot delete the old snapshot, because we get this error:

CWLLG3256I: The 'Dokumentum feldolgozás' task with the 'Task.33245' identifier is assigned to the 'TDM WF Admins_S_3b73bfc5-f165-4a91-9c9d-ae630f366e55.1a346c18-a1f6-4200-9fe6-aa9c6c0001ee' managers group with the 'UserGroup.12128' identifier. The task is in the 'Received' state. The task is part of the '9328 - Dokumentum szignálás' process instance with the 'BPDInstance.9328' identifier that is in the 'Active' state.
Explanation: The task is assigned to a managers group for the snapshot that you want to delete. The snapshot cannot be deleted before this reference is removed.
Action: Before retrying to delete the snapshot, reassign the task to a group in a different snapshot using the "Assign Task To Group" REST API or ensure that the task has completed and then delete it using the BPMTasksCleanup command.

We don't understand this, because - we suppose - the migration must migrate everything. How can it happen that a team assigned to a task migrated to the new snapshot references to a manager team which is in the old snapshot (if we understand well the cause of the error)? Its crazy...

Now we decided to wait until all the migrated tasks will be closed, and we will delete the old snapshot only after that, but we want understand what's behind this phenomenon. Or if anybody can help us to free up the old snapshot, we could delete the old snapshot earlier.

So, what's behind this and how to avoid in the future or solve these errors?

Thanks,

Do you use some sort of dynamic Team assignment for the task in question?  If so, I suppose it's possible that even after migrating the instances to a new snapshot, a task that was migrated remained assigned to a dynamic team asset that is still a part of the snapshot you're trying to delete.  Reassigning back to team or moving the token back to the task itself might help resolve the issue.

Thanks -Don

Hi All,

After successfully migrating all instances of all processes of an application to a new snapshot, we cannot delete the old snapshot, because we get this error:

CWLLG3256I: The 'Dokumentum feldolgozás' task with the 'Task.33245' identifier is assigned to the 'TDM WF Admins_S_3b73bfc5-f165-4a91-9c9d-ae630f366e55.1a346c18-a1f6-4200-9fe6-aa9c6c0001ee' managers group with the 'UserGroup.12128' identifier. The task is in the 'Received' state. The task is part of the '9328 - Dokumentum szignálás' process instance with the 'BPDInstance.9328' identifier that is in the 'Active' state.
Explanation: The task is assigned to a managers group for the snapshot that you want to delete. The snapshot cannot be deleted before this reference is removed.
Action: Before retrying to delete the snapshot, reassign the task to a group in a different snapshot using the "Assign Task To Group" REST API or ensure that the task has completed and then delete it using the BPMTasksCleanup command.

We don't understand this, because - we suppose - the migration must migrate everything. How can it happen that a team assigned to a task migrated to the new snapshot references to a manager team which is in the old snapshot (if we understand well the cause of the error)? Its crazy...

Now we decided to wait until all the migrated tasks will be closed, and we will delete the old snapshot only after that, but we want understand what's behind this phenomenon. Or if anybody can help us to free up the old snapshot, we could delete the old snapshot earlier.

So, what's behind this and how to avoid in the future or solve these errors?

Thanks,