Oct 05, 2023
Oct 20, 2023
Closed, Fixed and tested
Fixed an issue where caching may serve outdated content, even after content was republished. This situation arose when a content item remained untouched for the expiration period (default 12 hours) and is then was accessed before ASP.NET Core initiates a scan of expired items (default maximum 60s after expiration).
The cache duration for content was reduced to 1 minute when content was loaded in a scheduled job, thereby increasing the likelihood of this occurring for longer running jobs that triggers multiple reloads of content from the database.