{"version":"2.1.268","anchor":"session-message-cache-priming-now-merges-into-an-in-flight-c","canonical_anchor":"session-message-cache-priming-now-merges-into-an-in-flight-c","heading":"Session-message cache priming now merges into an in-flight cache entry instead of skipping","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/session-message-cache-priming-now-merges-into-an-in-flight-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Session-message cache priming now merges into an in-flight cache entry instead of skipping\n\nSession-message cache priming now merges into an already-in-progress cache load instead of dropping the new data\n\n**What**\n\nWhen Claude Code primes its cache of session message UUIDs and a cache entry for that session is already being built, it used to simply skip the new priming request and do nothing further. Now it waits for the in-flight cache load to finish and merges the newly supplied UUIDs into the resulting set.\n\n**Why**\n\nThis prevents UUIDs from being silently lost when two priming calls for the same session overlap, ensuring the cache ends up complete rather than missing entries that arrived while a load was already underway.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}