Provider
KlaviyoIncident detail
Elevated flow recipient skips
Resolved incidentMinor3 affected services
Timeline window
to
Get alerted the next time Klaviyo breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Monitoring
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.
Resolved
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.
Keep exploring
More from Klaviyo
Neighboring incidents on Klaviyo's timeline and the rest of their record on OutageDeck.