Replies: 29 comments 8 replies
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
The same thing happens to me |
Beta Was this translation helpful? Give feedback.
-
|
Same error on my side, its very inconsistent getting some hits and then some some failures on cache hits |
Beta Was this translation helpful? Give feedback.
-
|
Happened as well |
Beta Was this translation helpful? Give feedback.
-
|
We are also seeing this, hits the error (much) more often than not |
Beta Was this translation helpful? Give feedback.
-
|
This is a critical showstopper. Many CI workflows rely on caching done by previous steps, now they fail, making merging impossible. |
Beta Was this translation helpful? Give feedback.
-
|
Related issue: actions/cache#1621 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Same for me |
Beta Was this translation helpful? Give feedback.
-
|
On matrix strategy, some of the jobs are able to fetch the cache correctly |
Beta Was this translation helpful? Give feedback.
-
|
Same here. Very inconsistent, sometimes it works sometimes it fails |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. |
Beta Was this translation helpful? Give feedback.
-
|
same here 😞 |
Beta Was this translation helpful? Give feedback.
-
|
Me too, combined with HTTP Error 502 when using |
Beta Was this translation helpful? Give feedback.
-
|
same here |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
Same happening the pipelines are failing due to cache miss. |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
Same here |
Beta Was this translation helpful? Give feedback.
-
|
same here. |
Beta Was this translation helpful? Give feedback.
-
|
same here. Github has opened an incident last hour: https://www.githubstatus.com/ |
Beta Was this translation helpful? Give feedback.
-
|
still seeing these issues, it's flaky rn |
Beta Was this translation helpful? Give feedback.
-
|
we are having issues with cache too |
Beta Was this translation helpful? Give feedback.
-
|
Same. I'm much sure the cache exists, but it showed cache not found. |
Beta Was this translation helpful? Give feedback.
-
|
Almost a month and this ass does exist... Amazing |
Beta Was this translation helpful? Give feedback.
-
|
With GitHub Pages: 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? |
Beta Was this translation helpful? Give feedback.
-
|
Looking at your cache issue, there are several potential causes for this problem. Here's a systematic approach to troubleshoot: Key Mismatch Analysis:
This suggests the cache key generation is inconsistent between save and restore operations. Common Solutions: 1. Verify Key Generation Logic - 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
Verify you're restoring cache within the same scope where it was created. 3. Debug Cache Keys - name: Debug cache key
run: |
echo "Cache key would be: generated-repository-lib-${{ hashFiles('**/package-lock.json') }}"4. Cache Retention 5. Workflow File Changes 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. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried upgrading the version? |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
-
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
Beta Was this translation helpful? Give feedback.
All reactions