Iterable incident

Journey processing halted

Major Resolved View vendor source →

Iterable experienced a major incident on August 28, 2024, lasting 52m. The incident has been resolved; the full update timeline is below.

Started
Aug 28, 2024, 10:49 PM UTC
Resolved
Aug 28, 2024, 11:42 PM UTC
Duration
52m
Detected by Pingoru
Aug 28, 2024, 10:49 PM UTC

Update timeline

  1. identified Aug 28, 2024, 10:49 PM UTC

    Around 2:20 PM PDT, we detected that journeys processing has halted. During this time, journeys will not start consuming users, any running journeys will be stuck, and no campaigns in journeys will send until we resolve the issue. No data will be lost, and they will be backlogged. Our team is actively working to resolve this as soon as possible. Next update will be be at or before 4:10 PM PDT.

  2. monitoring Aug 28, 2024, 11:07 PM UTC

    We have identified and fixed the problem that halted journey processing. Journeys are now processing through the backlog and are recovering with no data loss. If you triggered a journey during this time, it is not necessary to retrigger it. No action is needed to ensure your journey is processing again.

  3. resolved Aug 28, 2024, 11:42 PM UTC

    The backlog has been processed and journeys are processing normally. There is no action needed to ensure any journeys you triggered during this time has processed. If you still see any issues, please reach out to our Support team.