Adobe Experience Manager: Keep custom schedulers disabled after upgrade or reinstall
After performing an Adobe Experience Manager (AEM) upgrade or application reinstall, previously disabled custom schedulers become re-enabled. This article explains how to identify affected schedulers and ensure they remain disabled to prevent unintended job executions.
Description description
Environment
Adobe Experience Manager (AEM) Managed Services, all supported LTS versions.
Symptoms
After an AEM upgrade or application reinstall, custom schedulers that were previously disabled are automatically re-enabled. This causes scheduled jobs to run unexpectedly, potentially impacting business processes or data integrity.
Cause
Application upgrades or reinstalls overwrite or reset scheduler configuration properties, resulting in schedulers being re-enabled even if they were previously disabled.
Resolution resolution
Follow the steps below to resolve the issue:
-
Log in to the AEM Author instance as an administrator.
-
Identify all custom schedulers that should remain disabled. Review your list of custom scheduler configurations or check the AEM Web Console or Configuration Manager for scheduler components with an
enabledproperty. -
For each affected scheduler:
a. Navigate to the scheduler configuration in the AEM Web Console or Configuration Manager.
b. Locate the
enabledproperty.c. Uncheck or set the
enabledproperty to false to disable the scheduler.d. Save the configuration.
-
Repeat this process for all custom schedulers that should remain disabled.
-
After completing these steps, verify that the schedulers remain disabled by checking their configuration status.
-
If you plan future upgrades or application reinstalls, document the list of schedulers that need to be checked and re-disabled as part of your post-deployment process.
-
(Optional) To automate verification, consider maintaining a script or checklist that queries the status of scheduler configurations after each deployment.