((new)) | Debug-action-cache

GitHub Actions cache behavior

Here’s an interesting, practical guide to understanding and debugging — specifically focusing on the actions/cache step and common "cache not restored" or "cache save failed" issues.

Alternative Tools (Beyond GitHub)

# List all caches for a repo gh cache list --repo owner/repo --limit 100 debug-action-cache

Where to set them:

Step 3: Validating Cache Integrity with Checksums

• Enable debug logging permanently for cache troubleshooting in a separate workflow.
• Use cache version prefix (e.g., v1-...) to allow manual invalidation.
• Regularly audit cache size with gh cache list --repo <repo>.
• For self-hosted runners, configure an external cache backend (e.g., @actions/cache with Azure Blob).

env: ACTIONS_RUNNER_DEBUG: true ACTIONS_STEP_DEBUG: true . For self-hosted runners

While different tools have different specific commands, the process of "debugging the action cache" generally follows these steps: 1. Inspecting Input Digests configure an external cache backend (e.g.