GitHub Actions / GitHub Actions

GitHub Actions Cache Service v2 Migration Breaking Workflows — Cache Not Found

Fix GitHub Actions workflows failing to restore build caches after GitHub's February 2025 cache service v2 migration, especially on self-hosted runners with outdated versions. Includes evidence for GitHub Actions troubleshooting demand.

Source-backed Last updated June 2, 2026 3 sources Needs local verification

Category: GitHub Actions
Error signature: Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures
Quick fix: Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.
Updated: June 2, 2026
Verification status: Source-backed
Evidence: 3 public source URLs

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for GitHub Actions, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures is a GitHub Actions failure pattern reported for developers trying to fix github actions workflows failing to restore build caches after github's february 2025 cache service v2 migration, especially on self-hosted runners with outdated versions.. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Herodevs blog and GitHub discussions document ongoing cache restore failures following the Feb 1, 2025 cache service deprecation. Self-hosted runners below v2.327.1 (required for actions/cache@v5) show 'Cache not found' despite successful saves. Multiple GitHub Discussions threads confirm this remains unresolved into March 2026. Distinct from the already-covered 'npm ci lockfile' error. High commercial impact — CI/CD pipelines for paid Teams plans blocked.

Common causes

Herodevs blog and GitHub discussions document ongoing cache restore failures following the Feb 1, 2025 cache service deprecation. Self-hosted runners below v2.327.1 (required for actions/cache@v5) show 'Cache not found' despite successful saves. Multiple GitHub Discussions threads confirm this remains unresolved into March 2026. Distinct from the already-covered 'npm ci lockfile' error. High commercial impact — CI/CD pipelines for paid Teams plans blocked.

Quick fixes

Confirm the exact error signature matches Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures.
Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures exactly before applying the quick fix.
Compare the failing environment with GitHub Actions versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures mean in GitHub Actions?

Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures indicates the workflow described by "GitHub Actions Cache Service v2 Migration Breaking Workflows — Cache Not Found" failed in a GitHub Actions context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures?

Check whether this cause matches your environment: Herodevs blog and GitHub discussions document ongoing cache restore failures following the Feb 1, 2025 cache service deprecation. Self-hosted runners below v2.327.1 (required for actions/cache@v5) show 'Cache not found' despite successful saves. Multiple GitHub Discussions threads confirm this remains unresolved into March 2026. Distinct from the already-covered 'npm ci lockfile' error. High commercial impact — CI/CD pipelines for paid Teams plans blocked.

Is the Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures guidance source-backed?

The "GitHub Actions Cache Service v2 Migration Breaking Workflows — Cache Not Found" page is labeled source-backed. It has 3 public source URLs from herodevs.com, github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures?

For "GitHub Actions Cache Service v2 Migration Breaking Workflows — Cache Not Found", avoid applying "Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Cache not found for input keys: generated-repository-lib-* — GitHub Actions Actions Cache v2 service migration causing intermittent cache restore failures?

For "GitHub Actions Cache Service v2 Migration Breaking Workflows — Cache Not Found", collect the failing GitHub Actions command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.