Looks like it’s currently set to be fixed in patch 11.0.2, which should be the next patch. Sorry for the delay.