Huge spike in MessagingService errors

Since yesterday MessagingService has been failing more than usual (error rate went up 10x or more), with these error messages:

The "Messaging | x failed, retrying" stuff is added by our logger. The rest of the message is returned from the API call itself. Also, we are now seeing error messages without a stack trace from MessagingService, something which has never happened before:

4 Likes

Hi,

We are aware of this and are looking into it. From our own logs, it seems like the issue has more or less been reduced. Can you confirm?

1 Like

I can confirm, seems to be more or less back to normal now. Thanks for the update!