[nicois]

So this is a big step forward in terms of avoiding the race condition where CI runners would accept new jobs during scale-in operations. But how do you ensure you only spawn new ephemeral runners as jobs become available? The webhook provides part of the answer, but do we need to use something like redis to ensure exactly one runner per queued job is started?

[sascha_sl]

It'd be nice if we had an API for all jobs that still need a runner, but I don't think that'll happen.