This should be resolved now!
It was reported elsewhere and I have both tested and received confirmation from affected users that it is working now, so I'm going to close this ticket. Feel free to respond if the issue persists for you!
And thank you for including the Event ID in your description of the issue!