Flow-triggering and real-time segmentation are now processing in real-time for all metrics. We are continuing to monitor all systems.
Posted Sep 25, 2020 - 17:41 EDT
Update
Flow triggering and segmentation delays have been reduced to 2 hours for the affected 12% of metrics. We currently project processing to be back to real-time in the next several hours. We are monitoring our systems and will post an update when processing is real-time.
Posted Sep 25, 2020 - 16:01 EDT
Update
Flow triggering and segmentation is still delayed by several hours for approximately 12% of metrics. We currently project processing to be back to real-time in 8-12 hours. We will post another update when we have a more accurate timeline.
Posted Sep 25, 2020 - 10:59 EDT
Update
Due to the volume of data accumulated between 7:30am on 9/23 and now, we currently expect event processing for flow triggering and segmentation to catch up within 12-15 hours. We are actively monitoring this issue and will provide further updates if our rate of progress improves.
As we catch up, flows will trigger if they have not been back-populated yet. No duplicate sends will occur if the flow has been back-populated. However, these sends will be subject to our flow triggering grace periods: for non-transactional flows, anything that should have gone out more than 4 hours ago will not be scheduled. For transactional flows, that grace period is 24 hours instead of 4 hours.
Posted Sep 24, 2020 - 18:53 EDT
Update
We have identified the root cause of this issue and a fix is in place. Our systems are in the process of catching up, but we do not have a good estimate for time to resolution at this time. We will post another update once an ETA is available.
Posted Sep 24, 2020 - 14:33 EDT
Identified
We have identified an issue impacting flow-triggering and segmentation for approximately 12% of metrics beginning at roughly 7:30am ET on Wednesday, 9/23. As a result, flows may not be triggering. We are working to resolve this issue as we speak, and will post further updates once we have an ETA to a resolution.
Posted Sep 24, 2020 - 12:51 EDT
This incident affected: Audience (Segments) and Flows (Processing).