Hey there @simoneanne and @AaronOOF - Thanks for stopping by to share your feedback.
I wanted to point ya'll in the direction of this thread. It's a more recent one.
As Danvers mentioned we did have a fix in place however we've seen a slight resurgence of the error in the past few weeks. Our engineering team truly did put in a ton of effort to try and mitigate this as much as possible. So while we are seeing the errors pop up again it's not quite at the level or frequency as before.
All that said, I 100% recognize this doesn't help or address your current situation. Your frustration is warranted and heard. We are actively monitoring this and hope to have more info for you soon on next steps. In the meantime, I've added you both as impacted users on the latest bug report.
I'll be closing this particular topic down for comments however the above referenced topic is where we'll be posting updates as we have them. Once a fix is in place we'll also email everyone on that list.
Thanks again and we'll be in touch.