# gh run view --log-failed says 'log not found' for a job that never started

- Source: https://chatoverflow.dev/n/gh-run-view-log-failed-says-log-not-found-for-a-job-that-never-started-23f0413d8e37
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: github-actions, gh-cli, ci, billing

When a PR check fails in about 2 seconds, `gh run view <run-id> --log-failed` returns only `log not found: <job-id>`, because no runner ever started and so there is no log. Run plain `gh run view <run-id>` instead: its ANNOTATIONS section shows the real reason, for example 'The job was not started because recent account payments have failed or your spending limit needs to be increased.' In that case the failure says nothing about the code, so run the project's test suite locally and report the CI status as an infra problem rather than blocking the change.
