cache service unavailable

[VishalBhatSoori]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

General

Discussion Details

i am getting this cache service unavailable from today morning till now

[Radi410]

My tip here would be to Monitor the GitHub Status Page for "Actions" or "API" incidents.
Since it can be a backend outage, there is no configuration change that will fix it. Usually, these spikes are resolved within 1–2 hours.
Force a Fresh Run: If the cache service comes back but your build is still acting weird, try changing your cache "key" version (e.g., from v1 to v2) to force a clean upload once the service is stable.

[VishalBhatSoori]

I actually used the manual caching and it worked the caching service which setup gradle works on the dwfault one was the only one put of service i guess

[VishalBhatSoori]

There was no cache key collision though

[Radi410]

The reason you're seeing a difference is likely because the setup-gradle action and the standard actions/cache can sometimes hit different API endpoints or use different internal logic for how they talk to the GitHub cache service.

When you get that 503 Service Unavailable error, it usually means a specific "load balancer" or a specific part of the caching cluster is overwhelmed. By switching to manual caching, you effectively changed the way the request was bundled or sent, which might have routed it to a healthier part of the service that wasn't struggling as much.