Course contentsShow
← Cloud and Infrastructure
Lesson 1696 of 2,98935. GitHub ActionsFree lesson

Workflow Run History and Re-runs

Navigating workflow run history, re-running failed workflows, and troubleshooting execution issues.

Workflow Run History and Re-runs

You'll learn how to navigate past workflow executions, re-run failed builds, and troubleshoot issues using GitHub Actions' history interface.

Understanding Workflow Run History

Every time a workflow executes, GitHub Actions records the complete run—every job, step, log line, and status. Think of it like your bank's transaction history: you can review what happened, when, and why. This history lives in the "Actions" tab of your repository and organizes runs chronologically by workflow.

Each run displays:

  • Trigger event (push, pull request, manual)
  • Branch or tag that triggered it
  • Overall status (success, failure, cancelled)
  • Duration and timestamp
  • Individual job statuses with expandable step logs

Navigating the History

From your repository, click the Actions tab. You'll see all workflows on the left sidebar. Select a workflow to view its run history. Click any specific run to drill into jobs and steps. Expand steps to see detailed logs—essential for troubleshooting failures.

Re-running Workflows

Failed workflows don't mean starting over from scratch. GitHub Actions offers several re-run options:

  • Re-run all jobs: Retries the entire workflow (useful for transient failures)
  • Re-run failed jobs: Only re-executes jobs that failed (saves time and resources)
  • Manual re-run: Trigger a workflow again from the UI even if it succeeded

This is invaluable when dealing with flaky tests, temporary network issues, or dependency download failures.

Troubleshooting with Logs

When jobs fail, dive into step logs. Look for error messages, exit codes, and timing patterns. Cross-reference with your workflow syntax to identify misconfigurations. The status and logs give you everything needed to diagnose and fix pipeline issues.

Key Takeaway: GitHub Actions' run history and re-run capabilities provide complete visibility into your pipeline executions, enabling quick troubleshooting and recovery from failures without losing valuable debugging context.