Skip to main content

Next action not regenerated following workstep deletion

In this article, we explore why a Child Protection next action may not regenerate following the deletion of a workstep.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

If you've added the wrong next action in a Child Protection workflow, the workaround is to delete the preceding step. This should allow you to re-add the correct next action.

The Delete Child Protection Worksteps function isn’t designed to handle deletion of incomplete worksteps. That’s because we expect you to make any necessary changes directly within the open step.

However, if the wrong workstep was selected as a next action, you’ll need to delete the previous workstep as well. If it’s a Child Protection step, Mosaic will automatically regenerate it so you can choose the correct next actions.

⚠️ Important: If you delete an incomplete Child Protection workstep by mistake, it won’t regenerate on its own.

To fix this:

  • Delete the previous workstep (if it’s a Child Protection step) to trigger regeneration.

  • If it’s not a Child Protection step, just re-open it and re-send the next action.

Examples

Assuming:

  • RCPC A completed with next action of RCPC B.

  • RCPC B is started and saved incomplete.

Error in open Child Protection workstep

Errors are made in the completion of RCPC B - these can be amended as the workstep is still open.


Incorrect Child Protection next action sent

RCPC B has been added in error - workstep can be deleted.
RCPC A should then also be deleted (obviously ensuring all the information is saved prior to this) and that will re-generate.
Start RCPC A, re-complete and add the correct next actions.


Incomplete workstep deleted in error

RCPC B is erroneously deleted while incomplete.
RCPC A should then also be deleted (obviously ensuring all the information is saved prior to this) and that will re-generate.
Start RCPC A, complete and add RCPC B again.

Did this answer your question?