Hi There,
I have created a purge scheduler config using local SDK, printed and saved configuration. However in config fields cron or interval field is missing. I deployed it on dev instance, however it did not run since last 4 days. Documentation for same does not specify how frequently does the purge scheduler runs. Some page quotes that it runs once a week.
Is there a way to change this schedule to run it more frequently or force trigger it
해결되었습니다! 솔루션으로 이동.
토픽은 커뮤니티 콘텐츠를 분류하여 관련성 있는 콘텐츠를 찾는 데 도움이 됩니다.
조회 수
답글
좋아요 수
Unfortunately, you cannot change or control the purge scheduler programmatically in AEMaaCS. However, if you need more frequent or targeted purging, here are a few options:
Custom workflow cleanup service (with caution)
You can create a custom OSGi service that:
Queries the var/workflow/instances path (using JCR or Workflow APIs).
Filters completed workflows older than a specific threshold.
Deletes them via WorkflowSession or JCR session (with care).
Hi @bagwanpankaj,
In AEMaaCS:
The purge services (eg. com.adobe.granite.workflow.purge.Scheduler) are managed internally by Adobe.
Adobe removed the cronExpression/scheduler.expression fields from customer configuration to avoid overload and ensure consistent system performance across Cloud environments.
The purge job typically runs weekly, but the exact timing is not always guaranteed or exposed.
If purge isn't running for more than a week, or content is growing unexpectedly:
Raise a DayCare/Support ticket with Adobe.
They can inspect job logs and force trigger if necessary.
Hi @SantoshSai,
I know that it runs once a week, Just wanted to know, if there is a way that we can control that programmatically or use tools like 'Bulk Workflow Remover' or via 'Manage Controlled Process', which is either removed or does not provide way to bulk remove workflow
조회 수
답글
좋아요 수
Unfortunately, you cannot change or control the purge scheduler programmatically in AEMaaCS. However, if you need more frequent or targeted purging, here are a few options:
Custom workflow cleanup service (with caution)
You can create a custom OSGi service that:
Queries the var/workflow/instances path (using JCR or Workflow APIs).
Filters completed workflows older than a specific threshold.
Deletes them via WorkflowSession or JCR session (with care).