DocumentationExperience Cloud KCS

Workflow Purge OSGi configuration value not reflecting correctly in AEMaaCS

Last update: August 18, 2026

In AEMaaCS, the Workflow Age value in the Workflow Purge OSGi configuration shows 30 days in the development environment, even though the configuration JSON sets it to 90 days. To fix this issue, update the property key format in the OSGi configuration file so the correct value appears at runtime.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service(AEMaaCS) – Sites
  • Instance: Development

Issue/Symptoms

  • The Workflow Age value for completed workflow audit node purging appears as 30 days instead of the intended 90 days in the development instance.
  • The OSGi configuration JSON for the workflow purge scheduler (for example, com.adobe.granite.workflow.purge.Scheduler.cfg.json) sets the value to 90 days, but the runtime configuration in the AEM as a Cloud Service environment does not reflect this.

Resolution resolution

To fix this issue, follow these steps:

  1. Open the OSGi configuration JSON file used for setting up workflow purge (for example, com.adobe.granite.workflow.purge.Scheduler.cfg.json in ui.config or your OSGi config module).

  2. Locate the following configuration value in the configuration JSON file:

    code language-none 
    // Configuration created by Apache Sling JCR Installer
{   "scheduledpurge.name":"Content Approval Workflow
Purge",   "scheduledpurge.daysold:Integer":90,
"scheduledpurge.purgePackagePayload":true,
"scheduledpurge.modelIds":[
"/var/workflow/models/qiddiya-corporate-
content-approval-workflow"   ]  }

  3. Remove the :Integer suffix from the property key so that only the base name remains (for example, change scheduledpurge.daysold:Integer to scheduledpurge.daysold).

  4. Save and commit your changes to your code repository.

  5. Deploy or redeploy your code so that the updated OSGi configuration is applied to your AEM as a Cloud Service development environment (via your Cloud Manager pipeline or RDE tooling as appropriate).

  6. In the AEM environment, verify that the Workflow Age value now reflects 90 days as expected (for example, via /system/console on local SDK or via the AEM as a Cloud Service Developer Console configuration dump).

Note

  • In AEM as a Cloud Service, .cfg.json OSGi configuration files must use plain property names (for example, scheduledpurge.daysold).
  • :Integer. AEM determines the type from the JSON value itself.
  • If you add type annotations, such as :Integer to property keys, AEM as a Cloud Service may ignore them or read them incorrectly, causing default or unexpected values at runtime.
recommendation-more-help
experience-cloud-kcs-help-kbarticles