Hi @savart

This issue got resolved from our end. Once deployed in production will update ASAP here.