Event-Triggered Journeys Delays Ingesting New Users

Incident Report for Iterable

Resolved

This issue is now resolved and the backlog is completely drained. Event trigger journey's as of 7:25 AM PST are back to normal and processing as expected.
If you still have any further questions please reach out to support@iterable.com.
Posted Dec 31, 2024 - 10:25 PST

Update

We are continuing to work on a fix for this issue.
Posted Dec 31, 2024 - 08:11 PST

Identified

Summary:
Event-Triggered Journeys Delays Ingesting New Users. The issue originated from errors in the workflow-entrance-trigger pods, causing a significant backlog in processing. There is no impact to Scheduled Journeys and API Triggered Journeys .
Actions Taken
The workflow-entrance-trigger service was updated to the latest version, and additional pods were scaled up to process the backlog faster. The deployment resolved the issue, and error rates dropped significantly.
Current Status
The errors we were experiencing have been fixed since 5AM PST, now we're just monitoring the backlog as it drains. For 99% of clients, the backlog has drained completely, there are a few stragglers with small backlogs
Next Steps
Engineers will continue monitoring error rates and ensure the backlog clears entirely. Follow-up tasks include setting up error rate monitoring and addressing journey-specific issues to prevent recurrence.
Posted Dec 31, 2024 - 06:29 PST
This incident affected: Global Web Application.