Hi
We have also identified this issue on our end.
Our development team has already implemented a fix, which will be included in an upcoming release.
In the meantime, please refer to the workaround described in the following post:
2 Likes