Flows are no longer skipping profiles with the skip reason "Incorrectly Triggered." As of 1:22 PM US/Eastern on October 29, 2026, we have finished reprocessing the impacted profiles so that eligible messages were sent. We apologize for any disruption this may have caused. This incident has been resolved.

Between 11:00 AM US/Eastern and 5:00 PM US/Eastern on October 28, 2026, some customers may have seen flows skip profiles with the skip reason "Incorrectly Triggered," shown in flow and profile activity. Flows are no longer skipping profiles for this reason, and we are reprocessing impacted profiles. No action is needed from customers, and we will confirm once reprocessing is complete. We continue to monitor closely.