Hi ​@natykarina 

I hope you're doing well, and thank you for reaching out to us through the Community.

We attempted to replicate the issue on our end and were indeed able to reproduce it successfully. Upon further investigation, it appears that the issue was caused by an internal change. That said, we’ve implemented a fix on our side.

Could you please verify if you are still experiencing the issue? If so, do let me know, and I will escalate your feedback to the appropriate teams.

Thank you, and I look forward to your confirmation.

Thanks for your feedback. I tested again and the error seems to be solved.

Great. Thanks for confirming ​@natykarina