Wasnt aware of it in .27.
Its a thing for sure, guaranteed in .22.
It was botched for at least 3 months befofe it got the .23 update that patched it (and created other issues).
On the plus side, maybe you can look over the .22 to .23 git commits to find out where the peoblem is and fix it locally in case this is indeed true again for .27…