Rerun failed jobs waiting for deleted runner

[plutoZZZZ]

Describe the bug
https://github.com/volcengine/vemlp-github-runner
We've encountered a issue with an action we've built, and we'd love to get some thoughts on it! This action is designed to elastically create and destroy self-hosted runners as needed.
However, we've noticed that when a user chooses to "rerun failed jobs," our setup job isn't triggered. As a result, no new runners are created, and the rerun jobs end up staying in a queue state indefinitely. It feels a bit off that the jobs keep waiting for a runner even after the original runner has already been destroyed.
We were wondering if there might be a good solution or workaround for this scenario? Any insights would be really appreciated!

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Run '....'
3. See error

Expected behavior
When "Rerun failed jobs" is selected, we expect the setup job (responsible for creating a new self-hosted runner) to trigger automatically. This would provision a new runner, allowing the rerun jobs to execute instead of remaining stuck in the queue.

Runner Version and Platform

Version of your runner?
latest
OS of the machine running the runner? OSX/Windows/Linux/...
Linux

What's not working?

Please include error messages and screenshots.

Job Log Output

If applicable, include the relevant part of the job / step log output here. All sensitive information should already be masked out, but please double-check before pasting here.

Runner and Worker's Diagnostic Logs

If applicable, add relevant diagnostic log information. Logs are located in the runner's _diag folder. The runner logs are prefixed with Runner_ and the worker logs are prefixed with Worker_. Each job run correlates to a worker log. All sensitive information should already be masked out, but please double-check before pasting here.