Dynamic Media TTL values do not update or display correctly
Dynamic Media TTL (Time-To-Live) configuration issues occur when cache duration changes do not appear in delivered assets. Common issues include TTL values remaining at previous settings, displaying as the Unix Epoch date, or using unsupported values. Update the TTL in the correct configuration source and validate CDN cache behavior to resolve the issue.
Description description
Environment
- Dynamic Media
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- AEM Managed Services
Issue/Symptoms
- Response headers continue to show previous TTL values after updates.
- TTL displays as Thu, 01 Jan 1970 00:00:00 GMT.
- Attempts to configure a TTL value of 0 fail.
- Smart Crop assets appear to ignore TTL changes.
- Recently updated cache settings are not reflected in delivered assets.
Cause
The issue occurs when existing CDN cache continues serving previously cached assets, TTL values are configured in the wrong location, unsupported TTL values are used, Smart Crop URLs inherit global TTL settings, or required cache-control headers are missing or configured incorrectly.
Resolution resolution
To resolve this issue, follow these steps:
- Identify whether your environment uses Dynamic Media Classic or Dynamic Media configuration and update the TTL in the appropriate location.
- Configure the required TTL value in the authoritative cache configuration.
- Republish a test asset and verify the updated TTL after the existing cache expires.
- Inspect the asset response headers and confirm that the Cache-Control value matches the configured TTL.
- Purge the CDN cache if immediate propagation is required and verify the updated response headers.
- Use supported TTL values only. The minimum supported TTL value is 1 hour.
- For Smart Crop assets, use rulesets if different TTL behavior is required.
Related Reading
recommendation-more-help
experience-cloud-kcs-help-kbarticles