Of course. I didn’t want to duplicate the other issue, but the bug is:
when using the English (United States) option for translation, it results in this error:
{"error"=>{"code"=>400, "message"=>"Invalid Value", "errors"=>[{"message"=>"Invalid Value", "domain"=>"global", "reason"=>"invalid"}]}}
The text is not translated. It does work for the standard English option, which is what we are currently using. I think some of our users are going to select the US option, though.