Our services aren't available right now
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Failed to save cache entry with path '/home/runner/.gradle/caches/modules-/files-////,zstd-without-long,1.0' and key: dependencies-bbe768bce32a4951f33733e21b487a97: Error:
Our services aren't available right now
We're working to restore all services as soon as possible. Please check back soon.
0u/B1aAAAAAAhhyIk/QZmR7+ycHTbZ7CJQ0hJMzBFREdFMDQxNwBFZGdlSince a few days I get error message like the one above when using the actions/cache@v4
Can you tell when your services are running again or if this is any issue on my side an the error message ist misleading.
- name: Cache Gradle packages
uses: actions/cache@v4
with:
path: |
~/.gradle/caches
~/.gradle/wrapper
~/.gradle/build-cache
key: XXX-${{ needs.env.outputs.branch }}-$GITHUB_RUN_NUMBER
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start with the actions/cache@v4 workflow step and its Gradle cache paths, then review the six comments for diagnosis; done would require an actionable, reproducible cause or a documented service-side resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100