{"version":"2.1.269","anchor":"cached-file-reuse-check-timestamp-handling-fixed","canonical_anchor":"cached-file-reuse-check-timestamp-handling-fixed","heading":"Cached file reuse-check timestamp handling fixed","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/cached-file-reuse-check-timestamp-handling-fixed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Cached file reuse-check timestamp handling fixed\n\nFixed a bug in the check that decides whether a cached file is still fresh enough to reuse\n\n**What**\n\nThe logic that decides whether a cached copy of a file is recent enough to reuse now correctly reads that file's own last-modified time (rounded down to the millisecond) before calculating its age. Previously it appears to have referenced a variable from the wrong scope.\n\n**Why**\n\nThis fixes the freshness check for cached files, making it correctly reflect the actual file's age rather than possibly using the wrong file's timestamp.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}