[debug] Download speed: 45.2 MB/s [debug] Parallel chunks: 4 [debug] Validation: SHA256 matches expected If you see Validation: SHA256 mismatch , your cache is corrupted (rare, but happens with network proxies). The solution is to delete the cache key. Let's map error symptoms to debug-action-cache insights.
The typical workflow looks like this:
[debug] Using key: 'build-cache-$ github.sha ' [debug] Cache created on: windows-2022 On Linux: debug-action-cache
gh actions cache delete <KEY> --repo <owner>/<repo> Or use the community action actions/delete-cache with that exact key. Once you have basic visibility, you can move to advanced diagnostics. 1. Segmenting the Cache Archive The cache action creates a .tar archive. Debug logs reveal segmentation: [debug] Download speed: 45
[debug] Compressing 1,234 files (245MB) [debug] Archive segmented into 3 parts [debug] Uploading part 1/3... If you see a segmentation error (e.g., Part 2 failed to upload ), you have a network issue or a file that changed during compression (race condition). A common mistake is mis-specifying the path . The debug log will show exactly what is being archived: The typical workflow looks like this: [debug] Using
You can query the GitHub API directly.
Then, in a workflow or locally: