In case anyone missed @289wk’s post above, we do have a fix coming in for this asap:
Appreciate everyone’s patience on this.