I am also not happy with this task, as again it specifies a solution, not an outcome. I much rather have "avoid expensive cleanup during the request to the degree this is possible" as acceptance criteria in the story.

If we instead go with a deferred update, as I suggested in T220150#5155352, then we probably won’t need a separate job class, since a deferred update can also just be a callable (anonymous function), and that should be enough in our case.

In T221703#5133388, @JeroenDeDauw wrote:

I am also not happy with this task, as again it specifies a solution, not an outcome. I much rather have "avoid expensive cleanup during the request to the degree this is possible" as acceptance criteria in the story.

Just to not ignore your comment here, this was a break down sub-task of a solution we previously agreed on in the parent task, hence it is more of a solution than a problem task.