"offline" runners stay in the list

[electroma]

I'm using a basic setup, but I see "offline" runners staying in the list.

Please suggest is it expected behavior?
Will it cause any issues over time?

[npalm]

We have the same issue. I think this will not create an issue over time. GitHub will remove runners older then 30 days. Runners are removed based on the list in github. If runners found in AWS that are not in GitHub they also removed. So, I see here two logical explanaties. First a spot-instances was killed by AWS. This will casue the orphan one in the list of GitHub. It is anyoing but not a big issue. The second cause could be that we have a bug in pagenation.

[BeyondEvil]

If you're like me, and the offline runners trigger your OCD, here's how I clean them up:

#!/bin/bash

for runner_id in $(gh api orgs/{org_name}/actions/runners --paginate --jq '.runners[] | select(.status == "offline") | .id'); do
  echo "Deleting runner: ${runner_id}"
  gh api --method DELETE "orgs/{org_name}/actions/runners/${runner_id}"
done

I had to auth using:

gh auth refresh -h github.com -s admin:org

gh is the Github CLI.