Hi Elias.
I’ll interject real quick to say that this has been confirmed to no longer occur in the upcoming 4.17 release. We are however evaluating whether we can identify what the specific fix was, and if so, whether we could include it in a possible 4.16.3 hotfix. Stay tuned.
Cheers