It doesn’t happen every time … not sure (yet) which version introduced this but started to seeing these error recently. Currently on v3.16.0