Jorge Turrado Ferrero

Could you share the ScaledObject that produces conflicts?

I'm not totally sure if KEDA should accept NULL as 0, or at least as default, because NULL is a failure indeed. SQL engines support handling this within the query...

Please, rebase your branch @cyrilico , the e2e issue was related with some breaking changes in otel-collector which are already fixed in `main` branch (your tests hasn't been executed yet...

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

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

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

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

@cyrilico I've merged 2 fixes to the e2e to trigger them again (you'll need to pull the changes :) )

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

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