GitHub Actions Diagnostic
Find the exact cause of your workflow failure
GitHub Actions Diagnostic is an interactive tool that identifies the exact cause of your workflow failure. Answer a short series of questions to get a specific fix with working YAML or shell commands.
What is happening with your GitHub Actions workflow?
- Workflow is not triggering at all
- Job fails with a permission error or "Resource not accessible by integration"
- Job or step is timing out or hanging
- Failures are intermittent — passes sometimes, fails sometimes
- Dependency installation fails (npm, pip, yarn, apt-get)
- Step fails with exit code 1 and unclear output
- Environment variable or secret is not available
- Cache is not working as expected
Diagnoses covered include: workflow file location errors, branch filter mismatches, fork pull request secret restrictions, GITHUB_TOKEN permission errors, secret name case mismatches, step timeouts, interactive prompt hangs, service container health checks, flaky tests, intermittent network errors, npm ci lockfile errors, peer dependency conflicts, pip version conflicts, SSL errors, exit code 1 debugging, environment variable scope issues, export not persisting between steps, GITHUB_ENV usage, step output with GITHUB_OUTPUT, cache key mismatches, and cache hit conditions.