Re-running workflows and jobs
You can re-run a workflow run, all failed jobs in a workflow run, or specific jobs in a workflow run up to 30 days after its initial run.
Who can use this feature?
People with write permissions to a repository can re-run workflows in the repository.
Tool navigation
In this article
Note
Re-run workflows use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. The workflow will also use the sameGITHUB_SHA (commit SHA) andGITHUB_REF (git ref) of the original event that triggered the workflow run.
Re-running all the jobs in a workflow
On GitHub, navigate to the main page of the repository.
Under your repository name, click Actions.
In the left sidebar, click the workflow you want to see.
From the list of workflow runs, click the name of the run to see the workflow run summary.
In the upper-right corner of the workflow, re-run jobs.
- If any jobs failed, select the Re-run jobs dropdown menu and clickRe-run all jobs.
- If no jobs failed, clickRe-run all jobs.
Optionally, to enable runner diagnostic logging and step debug logging for the re-run, selectEnable debug logging.
ClickRe-run jobs.
To re-run a failed workflow run, use the
run rerunsubcommand, replacingRUN_IDwith the ID of the failed run that you want to re-run. If you don't specify arun-id, GitHub CLI returns an interactive menu for you to choose a recent failed run.Shell gh run rerun RUN_ID
gh run rerun RUN_IDTo enable runner diagnostic logging and step debug logging for the re-run, use the
--debugflag.Shell gh run rerun RUN_ID --debug
gh run rerun RUN_ID --debugTo view the progress of the workflow run, use the
run watchsubcommand and select the run from the interactive list.Shell gh run watch
gh run watch
Re-running failed jobs in a workflow
On GitHub, navigate to the main page of the repository.
Under your repository name, click Actions.
In the left sidebar, click the workflow you want to see.
From the list of workflow runs, click the name of the run to see the workflow run summary.
In the upper-right corner of the workflow, select the Re-run jobs dropdown menu, and clickRe-run failed jobs.
Optionally, to enable runner diagnostic logging and step debug logging for the re-run, selectEnable debug logging.
ClickRe-run jobs.
To re-run failed jobs in a workflow run, use therun rerun subcommand with the--failed flag. ReplaceRUN_ID with the ID of the run for which you want to re-run failed jobs. If you don't specify arun-id, GitHub CLI returns an interactive menu for you to choose a recent failed run.
gh run rerun RUN_ID --failedTo enable runner diagnostic logging and step debug logging for the re-run, use the--debug flag.
gh run rerun RUN_ID --failed --debugRe-running a specific job in a workflow
On GitHub, navigate to the main page of the repository.
Under your repository name, click Actions.
In the left sidebar, click the workflow you want to see.
From the list of workflow runs, click the name of the run to see the workflow run summary.
Under the "Jobs" section of the left sidebar, next to the job that you want to re-run, click.
Optionally, to enable runner diagnostic logging and step debug logging for the re-run, selectEnable debug logging.
ClickRe-run jobs.
To re-run a specific job in a workflow run, use therun rerun subcommand with the--job flag. ReplaceJOB_ID with the ID of the job that you want to re-run.
gh run rerun --job JOB_IDTo enable runner diagnostic logging and step debug logging for the re-run, use the--debug flag.
gh run rerun --job JOB_ID --debugReviewing previous workflow runs
On GitHub, navigate to the main page of the repository.
Under your repository name, click Actions.
In the left sidebar, click the workflow you want to see.
From the list of workflow runs, click the name of the run to see the workflow run summary.
To the right of the run name, select theLatest dropdown menu and click a previous run attempt.