Hello Alena,

I guess one option would be to use an activity and restart the FLOW for this subcase.

Hi Alena,

I think the subcase assignment is not committed in DB. The probable reason could be a rollback happened internally. Pls run a DB trace to figure out if any rollback is happening at the backend or not.

It is difficult to predict the issue without having proper debug into your application. If the assignment is not present in the DB tables, then you can't restore straightaway without doing a DB restore. If this is not possible then you can being the flow on the subcase. Although this is not a proved solution.

Pls check : 

PEGA Button -- Process & Rules -- Tools -- Work Admin -- Worklist/Workbasket Assignment Errors

go to the above path in Pega you can find the list of error assignments

Hi Alena,

Can you try running the "Work-.FixProblemAssignments" activity by passing the pzInsKey of the case for which erroneous assignment exists and share the results.