Maybe it’s fixed now. It seems some clients were putting incorrect data in the reaction event’s content.