Runners in a stuck state after the Actions outage

[Scalahansolo]

Checks

• I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• I am using charts that are officially provided

Controller Version

0.9.1

Deployment Method

Helm

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions).
• I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

Cannot repro as this only happened due to the outage

Describe the bug

After the Actions outage yesterday, all of the runners in my runner group ended up in the following state. In the Github UI, it says this runner has an active job which is just a failed job due the outage.

The logs of the actual runner seem fine, and it's just waiting to be assigned a job properly.

Describe the expected behavior

I would have expected these failed jobs to not be listed as "active" in my runners. Im guessing because these failed jobs are still marked as active in by Github, new jobs are not being assinged to these runners.

Additional Context

N/A

Controller Logs

N/A

Runner Pod Logs

N/A

[nikola-jokic]

Transferred the issue here since it is related to the runner itself, and not ARC.

[Scalahansolo]

As a quick update here. The only way I could get these runners healthy again was I had to track down all those "Active Jobs" that were in the failed state (this took forever), and use the Github API to hard delete those runs out of Github. Once I deleted all of those, after a bit Github started to see those runners as idle and started to assign new jobs.