Thanks for feedback, itās a known issue we are working on, check the release explainer for V2.3.2 here,