Maintenance tasks do not run because of invalid configuration

Last update: June 27, 2026

Maintenance tasks can fail when the maintenance window configuration is missing required properties or contains invalid overrides. Correcting or removing the bad configuration restores normal scheduler behavior.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)
AEM Managed Services
Adobe Developer App Builder

Issue/Symptoms

Error logs show messages such as Start and/or end time invalid: null, null.
Logs display No maintenance windows found.
Maintenance tasks do not run on schedule.
Maintenance UI does not display expected tasks.
Tasks appear stopped even though logs indicate completion.

Cause

The system prioritizes configurations from the /conf path over /apps. If invalid or incomplete nodes exist in /conf, they override valid configurations, preventing the scheduler from loading proper maintenance window definitions. Incorrect values such as missing start and end times or mismatched task names cause failures.

Resolution resolution

To resolve this issue, follow these steps:

Review logs to identify errors indicating invalid maintenance window definitions.
Inspect configuration under /conf/global/settings/granite/operations/maintenance and identify incomplete or empty nodes.
Remove invalid configuration nodes that contain missing or incorrect values.
Validate configuration under /apps/settings/granite/operations/maintenance for required properties.
Ensure task identifiers such as granite.maintenance.name match expected values.
Redeploy corrected configuration through the standard deployment process.
Confirm that the maintenance UI shows the expected tasks.
Check the logs during the next scheduled window to confirm the tasks start and complete successfully.

recommendation-more-help

experience-cloud-kcs-help-kbarticles