Hi @anish-s . I had a look at the Workflow Remover but I don't think it
does what we need. If I understand correctly, the Workflow Payload Paths
you can specify in the Workflow Remover configuration only act as an
additional filter for determining if a workflow should be removed or
not.What we would like to have is that the payload of the workflow is
removed together with the workflow, but only if the payload is a
generated workflow package.
Thank you for your input. I find it quite hard to understand why there
is no OOTB solution in AEM for this. Isn't this a common problem when
using workflows? I mean that workflow packages are automatically
generated and pile up in the repository? Or are we doing something wrong
in our AEM/workflow setup?
Thank you for your answer but I'm afraid it doesn't address my question.
I was asking about generated workflow packages in /etc/workflow/packages
and not about packages created by the package manager.This shouldn't be
marked as the correct answer.
In our AEM 184.108.40.206 Author instance we are seeing a lot of generated
workflow packages (~1800) in /etc/workflow/packages. Much more than
there are running workflow instances. The Workflow Purge is configured
to remove COMPLETED workflows older than 30 days but this doesn't seem
to remove associated workflow packages.Is there a way to get rid of the
old workflow packages?