Thank you for the helpful description which helped us recreate this error on our end.

We are putting out a fix today.