Caching not working

[prati08]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

Actions Cache

Discussion Details

Verified cache is created,

but unable to download it or restore it using

getting below error
Cache not found for input keys: generated-repository-lib-12345465475746547576745757657653734573375

error
##[debug]Cache service version: v2
##[debug]Resolved Keys:
##[debug]["generated-repository-lib-b3dc82beb7447e11fe8ec8cc93d2255062b4ca6e"]
##[debug]Checking zstd --quiet --version
##[debug]1.5.7
##[debug]zstd version: 1.5.7
##[debug][Request] GetCacheEntryDownloadURL https://results-receiver.actions.githubusercontent.com/twirp/github.actions.results.api.v1.CacheService/GetCacheEntryDownloadURL
##[debug][Response] - 200
##[debug]Headers: {
##[debug] "content-length": "56",
##[debug] "content-type": "application/json",
##[debug] "date": "Wed, 18 Jun 2025 10:41:00 GMT",
##[debug] "x-github-backend": "Kubernetes",
##[debug]}
##[debug]Body: {
##[debug] "ok": false,
##[debug] "signed_download_url": "",
##[debug] "matched_key": ""
##[debug]}
##[debug]Cache not found for version 2b8f23c3424597ca704ee4c4e20b46e1ec8212372b530f2cc52240b6d527d6c9 of keys: generated-repository-lib-b3dc82beb7447e11fe8ec8cc93d2255062b4ca6e

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[rruanosporttia]

The same thing happens to me

[hugos99]

Same error on my side, its very inconsistent getting some hits and then some some failures on cache hits

[mahdiar-naufal-shyftplan]

Happened as well

[MathConstant]

We are also seeing this, hits the error (much) more often than not

[ArtemGoutsoul]

This is a critical showstopper. Many CI workflows rely on caching done by previous steps, now they fail, making merging impossible.

[ArtemGoutsoul]

Related issue: actions/cache#1621

[alejandrocelada-wiser]

We're also experiencing the same issue across multiple pipelines. Definitely seeing flaky behavior with GitHub Actions cache — it intermittently fails to restore even when the key clearly exists. This is currently blocking parts of our development and CI workflows. Looking forward to any updates or workarounds. Thanks to everyone sharing here.

[v-zamora]

Same for me

[mahdiar-naufal-shyftplan]

On matrix strategy, some of the jobs are able to fetch the cache correctly

[tapsouza]

Same here. Very inconsistent, sometimes it works sometimes it fails

[ckrivacic01]

I am also seeing the same issue using cache v3 in my actions. Everything was fine two days ago but today something is not working.

        id: cache-jars
        uses: actions/cache@v3

[MelDommer]

Same issue here.

[brunorafa]

same here 😞

[Hermanverschooten]

Me too, combined with HTTP Error 502 when using gh run watch a lot. This started last night around 19:00 Europe/Brussels for me.

[Hermanverschooten]

I just ran a GH action to first builds and then later deploys the build code. The build creates a cache that is then consumed in the deploy. The deploy step was compiling again because the cache was not there. These errors were given:

ANNOTATIONS
! Failed to save: reserveCache failed: Cache service responded with 503
deploy: .github#3

! Failed to restore: getCacheEntry failed: Cache service responded with 503
deploy: .github#11

[oleg-andreyev]

same here

[oleg-andreyev]

https://github.com/orgs/community/discussions/27059#discussioncomment-13510347

[oleg-andreyev]

it happened again...

[natanoelk]

Same here

[muhammadamer-10P]

Same happening the pipelines are failing due to cache miss.

[henripqt]

Same here

[raubel]

Same here

[PargRi01]

same here.
Cache created in one job, next job cannot get a hit.

[tanin47]

same here.

Github has opened an incident last hour: https://www.githubstatus.com/

[nrgbistro]

Looks like they removed it from the status page but I'm still getting the same issue

[tanin47]

still happens to me too

[jrh-exacta]

we are still see these issues even though the Status Page says they are resolved.

[ereesor-ag]

I'm still seeing this on our workflows
EDIT: We are using actions/cache@v4 and I manually checked an earlier cache hit with the same key in the same workflow run

[shivam-ajmera]

still seeing these issues, it's flaky rn

[nataliasantostheguarantors]

we are having issues with cache too

[inexistence]

Same.

I'm much sure the cache exists, but it showed cache not found.

Cache hit for: Linux-cache_ids-c07ea781e5474a6ae3aea6bd8ae7d2a54ba86ad6f4e952ed2998f2efe41cd3d9
Warning: Failed to restore: 
Cache not found for input keys: Linux-cache_ids-c07ea781e5474a6ae3aea6bd8ae7d2a54ba86ad6f4e952ed2998f2efe41cd3d9, Linux-cache_ids-

[RusJJ]

Almost a month and this ass does exist... Amazing

[kgierach]

With GitHub Pages:
Failed to save: reserveCache failed: Cache service responded with 503

The GitHub pages site never updates when I make changes and try to publish. I think I know the root cause: I deleted my non-functional repository and then made a new simpler one (which actually builds), but with the same REPO name "kgierach.github.io", in order to publish the blog.

Is there any way to invalidate the cache or force the push?

[RusJJ]

With GitHub Pages: Failed to save: reserveCache failed: Cache service responded with 503

The GitHub pages site never updates when I make changes and try to publish. I think I know the root cause: I deleted my non-functional repository and then made a new simpler one (which actually builds), but with the same REPO name "kgierach.github.io", in order to publish the blog.

Is there any way to invalidate the cache or force the push?

5xx errors basically mean server error. There's something with cache servers and this problem exists for month+

[jainamjain-dev]

Looking at your cache issue, there are several potential causes for this problem. Here's a systematic approach to troubleshoot:

Key Mismatch Analysis:
Your error shows two different cache keys:

• Search key: generated-repository-lib-12345465475746547576745757657653734573375
• Resolved key: generated-repository-lib-b3dc82beb7447e11fe8ec8cc93d2255062b4ca6e

This suggests the cache key generation is inconsistent between save and restore operations.

Common Solutions:

1. Verify Key Generation Logic
Ensure your cache key generation is deterministic:

- name: Cache dependencies
  uses: actions/cache@v3
  with:
    path: |
      ~/.cache
      node_modules
    key: generated-repository-lib-${{ hashFiles('**/package-lock.json', '**/yarn.lock') }}
    restore-keys: |
      generated-repository-lib-

2. Check Cache Scope
Caches are scoped to:

• Repository
• Branch (and default branch)
• Workflow run context

Verify you're restoring cache within the same scope where it was created.

3. Debug Cache Keys
Add debugging to see actual key values:

- name: Debug cache key
  run: |
    echo "Cache key would be: generated-repository-lib-${{ hashFiles('**/package-lock.json') }}"

4. Cache Retention
GitHub Actions cache has a 7-day retention period and 10GB limit per repository. Old caches may be evicted.

5. Workflow File Changes
If you've modified the workflow file, ensure the cache key logic remains consistent across commits.

Quick Fix to Try:

- name: Restore cache
  id: cache-restore
  uses: actions/cache/restore@v3
  with:
    path: your-cache-path
    key: generated-repository-lib-${{ hashFiles('your-lock-file') }}
    restore-keys: |
      generated-repository-lib-

- name: Debug cache hit
  run: echo "Cache hit: ${{ steps.cache-restore.outputs.cache-hit }}"

Can you share your actual workflow YAML for the cache save and restore steps? This would help identify the specific key generation issue.

[FroyaTheHen]

Have you tried upgrading the version?

We are deprecating some versions of this action. We recommend upgrading to version v4 or v3 as soon as possible before February 1st, 2025.