Ghost offline runners accumulate when spot instances are terminated

[yongwww]

GitHub runner registrations remain in "offline" state after EC2 instances are terminated (e.g., spot interruption). The scale-down Lambda only iterates over existing EC2 instances to find orphaned runners, but doesn't check GitHub runners for missing EC2 instances. This causes offline runners to accumulate over time. any ideas about it?

[Brend-Smits]

Hey @yongwww

I think this will be fixed by #5055
Just an FYI :)

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs. Thank you for your contributions.