Runs
The Runs page shows recent workflow runs across all your repositories, making it easy to see what's happening right now.
Runs List
Navigate to Runs in the sidebar to see recent runs grouped by repository.
Organization
Runs are grouped by repository with:
- Pinned repositories first
- Then sorted by most recent run
- Each repository shows up to 30 recent runs
Run Information
Each run row displays:
| Column | Description |
|---|---|
| Workflow | Workflow name with link to GitHub |
| SHA | First 7 characters of the commit |
| Branch | Branch that triggered the run |
| Actor | GitHub username who triggered |
| Event | Trigger type (push, pull_request, etc.) |
| Duration | How long the run took |
| Attempts | Number of attempts (highlighted if > 1) |
| Result | Status badge with conclusion |
| When | Relative time (e.g., "5 minutes ago") |
Status Badges
| Badge | Meaning |
|---|---|
| success (green) | Run completed successfully |
| failure (red) | Run failed |
| cancelled (gray) | Run was cancelled |
| timed_out (yellow) | Run exceeded time limit |
| running (blue, animated) | Run is currently in progress |
| queued (yellow) | Run is waiting to start |
Flaky Indicator
Runs that succeeded after being re-run show a "flaky" badge. This helps identify tests that pass inconsistently.
In-Progress Runs
Active runs appear with:
- Animated blue "running" badge
- Duration shows "-" (not yet known)
- Will update on page refresh
Runless receives webhook events in real-time, so in-progress runs appear within seconds of starting.
Viewing Run Details
Click the external link icon to view the full run details on GitHub, including:
- Complete logs
- Job breakdown
- Artifacts
Time Range
The Runs page shows runs from the last 30 days, limited to the 500 most recent runs across all repositories.
Filtering
Use the repository filter to focus on specific repos:
- Click the filter dropdown
- Select repositories or a saved group
- The runs list updates to show only matching runs
Common Workflows
Investigating a Failure
- Find the failed run in the list
- Note the commit SHA and branch
- Click through to GitHub to see the logs
- Check if other runs at the same SHA also failed
Tracking Re-runs
Look for runs with "Attempts: 2" or higher. These indicate:
- Someone manually re-ran a failed workflow
- A flaky test eventually passed
- Infrastructure issues that resolved on retry
Seeing What's Running Now
Look for blue "running" badges at the top of each repository section.