For complex technical issues or bugs like this, it is highly recommended that you directly contact support as it can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what you have access to. Additionally, sharing sensitive information about your situation might not be suitable for an open forum discussion.
If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.
I’m sorry to hear that you’re encountering this issue. However, I can confirm that we haven’t received any recent reports from other users with similar problems. The original issue you’re referencing was addressed with a fix released in May 2023.
As @samliew suggests, in cases like these, it’s always recommended to open a ticket with us. Our support team is equipped with the right tools to investigate this and, if needed, escalate it to the developers for further attention.