Eldarrin

damn, written and deleted a response twice. I see it now, but does it really matter as the system is working and the change will at most affect microseconds? But...

> I'm worried about it because I have executed e2e tests twice and both times `azure_pipelines_test` has failed. Could you check it @ramondegoede ? quick check pat tokens didn't expire?...

So, not for merging IMHO

Just an idea, what about jobs rather than objects as they avoid the HPA? Job can be a simple stamper to interface with the metric gatherer. Last time I did...

There only possible scenario I can see is that the scalers use a shared state model, but the problem here is that keda is just queuing what ADO pipelines says...

The problem is with state. Keda scalers are stateless. It just checks the length of the queue and creates enough agents for it; it is not for Keda to check...

Optional will be good, and it will double the api calls so rate-limits are a concern if you have many scalers variants running