Hello, we’re aware of the issue and it has already been fixed internally, it should be present in an upcoming patch.