Indeed this was a bug on the client. It has been fixed now. The fix won’t be live until next client update. Thank you!