DocumentationExperience Cloud KCS

AEM as a Cloud Service: Workflow Purge Scheduler activation and timing

Last update: October 22, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article describes the expected behavior of the Workflow Purge Scheduler in Adobe Experience Manager as a Cloud Service, including its activation status and when the purge job is executed after deploying configuration through the pipeline.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (all versions)

Symptoms

  • After deploying the com.adobe.granite.workflow.purge.Scheduler.cfg.json configuration file via pipeline, the scheduler component in the Developer Console shows an “Activation Delayed” status.
  • There is uncertainty about when the workflow purge maintenance task is executed.
  • No errors are reported, but the timing and activation behavior are unclear.

Cause

The “Activation Delayed” status is normal for the workflow purge scheduler. This component is designed to activate only during its scheduled maintenance window. The purge job runs automatically based on the defined schedule in the configuration file.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Confirm that the configuration file com.adobe.granite.workflow.purge.Scheduler.cfg.json has been deployed to the correct path via pipeline.
  2. Understand that the “Activation Delayed” status in the Developer Console is expected for this component. It indicates the scheduler is in a lazy activation state and will start when triggered by its schedule.
  3. The workflow purge job is scheduled to run automatically during the weekly maintenance window, which is every Saturday at 01:00 UTC by default in AEM as a Cloud Service.
  4. No additional configuration is required unless a different schedule is desired.
  5. If a custom schedule is needed, update the configuration file accordingly and redeploy.
  6. After deployment, the first purge run with the new configuration will occur at the next scheduled maintenance window.
  7. If there are many workflow instances, multiple runs may be required to complete the purge.
recommendation-more-help
experience-cloud-kcs-help-kbarticles