I am running into this issue aswell. Could you also add me to the list to notify me when this issue is resolved

Im having the same issue.
 

Hi there @LvdB and @Vitor R,

We’ve added you both to the bug report which will help to increase it’s priority. As ever, we can’t give any estimates as to when you can expect this to be resolved by but we’ll definitely let you know once it is. Thanks for everyone’s continued patience here in the meantime, it’s much appreciated!  

I have the same issue. Please add me to the list as well.

Sorry for the delay here @Ben06. I’ve added you to the list and will be in touch as soon as it’s fixed! 

Same issue here! 

So sorry to hear that @DebJ. I’ve added you to the list so you can expect to receive an email notification from us once it’s been sorted.

In the meantime, I’ve just seen a mention of this happening when there are special characters being used in the event name. I expect that’s not the cause of these errors in every single instance but thought it worth mentioning in case removing special characters from the event name helps to resolve things in some cases. If anyone here gives that a try and it works please do let us know!