I wonder if this is related to a bug that was introduced in 2.2.0 which was fixed in an update 2.20.130