Thank you, Hans!
v4.3.1 has been rolled out.
I hope it should work as expected on your environment (as I’ve never got this issue)
Why it happened only on some users was due to the timing of internal modules.
Sorry for the trouble and thank you for reporting it, guys!
Please let me know if it still persists.
The patch fixed the issue. Thank you!
Sorry, was away for a few days, but can confirm that the issue is gone in 4.3.2. Hope you got some sleep eventually!