Thanks for the report, Mayoyama!
This would appear to be a system-side macro issue.
We'll look into it and do our best to get it fixed in the near future!