The issue was related to performance issues with the inngest platform yesterday in addition to memory exceptions being thrown by our inngest workers during follow-up sending.

We have deployed a fix and this issue should now be resolved.

We are aware of an issue impacting some core flows resulting in delayed message sends and the delivery of follow ups.

We're investigating and will update shortly.