hello @bab85 Yes, this bug has already been reported, it’s being discussed here:
But I thought it was fixed with version 4.32
