What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To rerun only the unsuccessful work in GitHub Actions, open the failed workflow run and choose Re-run jobs > Re-run failed jobs. You can do the same from the GitHub CLI with gh run rerun RUN_ID --failed. GitHub permits reruns for up to 30 days after the original run and limits each run to 50 reruns total. A rerun keeps the original triggering actor’s privileges and the original commit SHA and ref.
Rerun failed jobs in the GitHub web interface
- In your repository, open Actions.
- Select the workflow, then open the failed run.
- Choose Re-run jobs > Re-run failed jobs.
- Optionally enable Enable debug logging if you need additional runner or step diagnostics.
- Select Re-run jobs to start the retry.
GitHub reruns failed jobs and the jobs that depend on them. Successful jobs that are not dependencies are not rerun. If you need to retry a different scope, use the menu’s other rerun options or the CLI/API options below.
Rerun failed jobs with GitHub CLI
Install and authenticate the GitHub CLI, then run this from a repository checkout or otherwise specify the relevant run ID:
gh run rerun RUN_ID --failed
Replace RUN_ID with the numeric workflow run ID. To request debug logging for the rerun, add --debug:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
gh run rerun RUN_ID --failed --debug
If you leave out RUN_ID, the CLI offers an interactive menu for choosing a recent failed run. The CLI command reruns failed jobs and their dependencies, rather than rerunning every successful, unrelated job.
Choose the right rerun scope
| What you want to rerun | How | What happens |
|---|---|---|
| Only failed jobs | Web: Re-run jobs > Re-run failed jobs; CLI: gh run rerun RUN_ID --failed |
Retries failed jobs and dependent jobs. |
| The entire workflow run | Choose the full-run option in the run’s Re-run jobs menu, or use gh run rerun RUN_ID. |
Reruns all jobs in the workflow, including jobs that succeeded previously. |
| One specific job | Use the specific-job option in the run’s Re-run jobs menu, or use the corresponding REST API endpoint. | Targets that job; dependent jobs may also need to run. |
Menu wording or placement may vary as GitHub updates its interface. Confirm the selected scope before starting, especially when a workflow has expensive or time-consuming successful jobs.
Rerun a workflow programmatically with the REST API
GitHub’s REST API provides endpoints to rerun a whole workflow run, rerun failed jobs, or rerun a specific job. The endpoints use the workflow run ID (and, for a specific-job rerun, the job ID). Fine-grained personal access tokens need Actions repository write permission. For the failed-jobs endpoint, GitHub reruns failed jobs and their dependent jobs.
See GitHub’s endpoint details and request formats in the REST API documentation for workflow runs. Use the API endpoint matching the scope you intend; do not substitute a run ID for a job ID.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCheck logs before you retry
A rerun is useful when a failure may be transient, but it does not fix a reproducible problem in the workflow, code, or environment. First identify the failed step and review its output so you can decide whether a retry is appropriate.
- Open the run summary and locate the failed job and step.
- Inspect the step output for the actionable error, such as a failed command or unavailable dependency.
- For CLI inspection, run
gh run view RUN_IDto view run details. - To print a job’s log, use
gh run view --job JOB_ID --log.
GitHub documents how to view and search workflow logs and how to troubleshoot workflows.
Limits and context that carry into a rerun
- Time window: workflows and jobs can be rerun up to 30 days after the initial execution.
- Rerun cap: a workflow run can be rerun at most 50 times total. The cap counts full reruns and reruns of subsets, not just whole-workflow retries.
- Actor privileges: the rerun uses the privileges of the actor who triggered the original run, not necessarily the person who clicks rerun.
- Same commit and ref: the rerun uses the original
GITHUB_SHAandGITHUB_REF. It does not pick up a newer commit automatically.
These are GitHub’s documented product limits and rerun behavior; check the linked documentation if they are critical to an operational policy.
Troubleshoot common rerun problems
The rerun option is unavailable
Check whether the original run is still within GitHub’s 30-day rerun window and whether it has reached the 50-rerun cap. Also confirm that your account has permission to access and act on the repository’s workflow runs.
The rerun used the wrong permissions or old code
This is expected behavior: GitHub reuses the original triggering actor’s privileges and the run’s original SHA and ref. If the workflow needs a newer commit or different authorization context, trigger a new workflow run under the intended conditions instead of retrying the old run.
The retry fails at the same step
Review the failed step’s log rather than repeatedly rerunning it. Correct the underlying workflow, code, secret, dependency, or environment issue as appropriate, then start a new run for the corrected commit.
You reran more work than intended
Before confirming a rerun, check whether you selected the full workflow, failed jobs, or a specific job. The full-run option includes previously successful work; the failed-jobs option includes dependencies needed by failed jobs.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup:
ScreenshotNeo is a website screenshot API and MCP server, not a way to rerun GitHub Actions jobs. If you need a clean screenshot of a workflow page or another URL, one GET request can return an image or PDF. For example:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://github.com -o shot.webp
See the ScreenshotNeo API documentation for request options. Cookie banners, popups and chat widgets are removed before capture; bot checks, blank pages and failed loads are never billed; an MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up free.
Frequently Asked Questions
Does rerunning a failed job create a new workflow run?
No. It reruns work within the existing workflow run, subject to that run’s rerun limit.
Can I rerun a failed job after pushing a fix?
A rerun uses the original commit SHA and ref. To run the pushed fix, start a new workflow run for that commit.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
