AEM timezone and timestamp issues across Cloud Service and managed environments
Timezone and timestamp issues in AEM can cause incorrect or inconsistent time display across user interfaces, logs, and scheduled operations. These issues often arise from UTC-only behavior in cloud deployments, reliance on system time in on-prem environments, or known limitations in specific UI components. Differences between expected local time and actual displayed time, as well as scheduling misalignment, are common outcomes. Resolution involves identifying the deployment type and aligning configurations, expectations, or scheduling logic accordingly.
Description description
AEM processes and displays time differently depending on the deployment model. Cloud-based environments use UTC for all time-related operations, while on-prem environments rely on the system clock. Certain UI features may also display inconsistent or incorrect time values due to known limitations or configuration issues.
Environment:
- AEM as a Cloud Service
- AEM Managed Services
- AEM 6.5 On-Prem
Issue/Symptoms:
- Timestamps appear in UTC instead of local time
- Inconsistent time display across different UI components
- Scheduler jobs execute at unintended times
- Date fields include time when not expected
- Mismatch between timestamps shown in different views
- Content dates display incorrect values
Root cause:
AEM as a Cloud Service enforces UTC for all server, UI, and scheduler operations, which cannot be modified. On-prem environments depend on the system clock, which may become misaligned due to configuration issues or daylight saving time changes. Additionally, certain components and UI elements have limitations or defects that lead to incorrect or inconsistent time display.
How to confirm
- Identify the deployment type to determine expected timezone behavior.
- Compare timestamps across different UI views for inconsistencies.
- Review scheduler execution times against expected local time.
- Check logs to confirm timestamps are recorded in UTC.
Resolution resolution
To resolve the issue:
- Align expectations with UTC behavior in cloud environments.
- Convert scheduled task times from local time to UTC when configuring jobs.
- Adjust metadata field configurations if date-only display is required.
- Apply available fixes or updates for known UI or component issues.
- For on-prem environments, update the system clock and restart services when changing timezone or daylight saving settings.