This is a bug in 2022.1.1 which should be fixed in 2022.1.2
I would recommend anyone using 2022.1.0 or 2022.1.1 to upgrade.