Jorge Turrado Ferrero

/run-e2e temporal **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/11650686342)

I see the use case of this feature, but IMHO we should expose the aggregation algorithm if we allow multiple queries in the same trigger. If you check the RabbitMQ...

/run-e2e ibm **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/11370385085)

> > PTAL @zbynek > > I guess you meant @zroubalik lol, sorry :( yes... I meant @zroubalik

/run-e2e ibm **Update:** You can check the progress [here](https://github.com/kedacore/keda/actions/runs/11692162546)

Hello Could you share KEDA operator logs?

any idea @kedacore/keda-core-contributors ?

Hello I think that the problem is related with the operator pod rather than the metrics server pod. Do you see any error on KEDA operator pod? The metrics server...

Do you see if the CPU is throttled?

There is throttling the in operator: ```bash Waited for 1.03611623s due to client-side throttling, not priority and fairness, request: PATCH ``` You will need to increase the kubernetes client values...