Thank you Mateusz. That's great news. It was driving us a bit crazy. Can you maybe explain why we only picked up this issue on the Azure-hosted VM and not on our other demo and dev and QA instances (which are hosted on our private infrastructure)? Is there something unique about the Azure VM that's trigger this issue? regards Andrew