Previous incidents

There was a partial 17-minute unavailability of the API caused by a network component issue. Our engineering team promptly identified and resolved the issue.

Our team identified a situation where messages were held in a sending state due to specific conditions: when a timing-policy was set on the campaign, the "When off-schedule, reschedule to next available timeframe" option was activated, and a trigger arrived outside the enabled time policy.
Another case that could cause these delays, is when a user passes the max number of daily messages, and the journey is set on "On communication block: RESCHEDULE".

This issue resulted in delays of 1-4 ...