@Jim I guess the product team didn’t fix this in 2.2.0, it’s still a bug…
And broke working things in the process!