#27553

The issue is introduced in one of v351 betas. It is going to be fixed with the forthcomming release.