yes we were using v1.21.0. we now tried 1.19.1 and dont have this issue