# This request was automatically failed because there were no enabled runners online to process it for more than 1 day

- **ID:** `cicd/github-actions-disk-space`
- **Domain:** cicd
- **Category:** system_error
- **Error Code:** `RUNNER_OFFLINE_TIMEOUT`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

GitHub Actions workflow triggered but no matching runner (self-hosted or GitHub-hosted) was online and enabled to accept the job for over 24 hours, causing the request to expire.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| GitHub Actions runner 2.311.0 | active | — | — |
| GitHub Enterprise Server 3.10 | active | — | — |

## Workarounds

1. **Check runner status via GitHub UI: Settings > Actions > Runners. If offline, re-run the config script on the runner machine: `./config.sh --url https://github.com/your-org --token NEW_TOKEN` then `./run.sh`** (85% success)
   ```
   Check runner status via GitHub UI: Settings > Actions > Runners. If offline, re-run the config script on the runner machine: `./config.sh --url https://github.com/your-org --token NEW_TOKEN` then `./run.sh`
   ```
2. **Provision a new runner instance if the old one is unrecoverable: use GitHub's auto-scaling runner setup or create a fresh VM with the latest runner version** (95% success)
   ```
   Provision a new runner instance if the old one is unrecoverable: use GitHub's auto-scaling runner setup or create a fresh VM with the latest runner version
   ```

## Dead Ends

- **** — If the runner's token has expired or the runner is registered to a different org/repo, restarting alone won't reconnect it to the correct workflow queue (65% fail)
- **** — Re-triggering without an available runner will just queue the job again, leading to the same timeout after another 24 hours (90% fail)