Why a Klaviyo flow is not sending and how to fix it

A Klaviyo flow usually fails to send because the flow is not live, the trigger event never arrives, or a filter or suppression rule removes the person. Work from the trigger outward and test with a real profile.

Have this ready.

• Access to the flow and to a test customer profile
• Knowledge of which store action should trigger the flow
• Access to your ecommerce integration settings
• An example customer who should have received the email but did not

Steps.

1. 1. Check the flow status

   Open Flows and confirm the flow is live and not in draft or manual mode. Also check that each email step is live, because a draft email inside a live flow will skip people.

2. 2. Confirm the trigger fires

   Look at the profile of someone who should have entered and read their activity feed. If the trigger event is missing, the problem is the integration, not the flow.

3. 3. Check the integration

   Open your integrations and verify the store connection is healthy. Reconnect if needed, then place a test order or action and see if the event appears.

4. 4. Review flow filters

   Read the trigger filters and flow filters carefully. A filter that is too strict, such as requiring a property that is often empty, will quietly block most people.

5. 5. Look at the profile's status

   Check whether the person is suppressed, unsubscribed or missing consent for email. These contacts are skipped even when everything else is correct.

6. 6. Check sending limits

   Review smart sending and any other frequency settings. A recent message may have caused the system to skip this one, which is normal behaviour but surprising.

7. 7. Test end to end

   Trigger the flow with a fresh test profile that meets every condition and watch it move through. Fix the first step where it stops, then retest.

Common pitfalls.

• Editing a live flow so that people already inside it behave unexpectedly.
• Assuming a missing email means a bug when a filter did its job.
• Testing with an internal address that is suppressed from earlier sends.
• Forgetting that time delays mean the email may simply not be due yet.

Check it worked.

• Flow and every email step show as live
• Trigger event appears on the test profile
• Test profile passes all filters
• Test profile is subscribed and not suppressed
• Test email arrives after the expected delay

Klaviyo changes its interface from time to time, so treat the steps as the order of work and match the names to what you see on screen.

Rather have this done for you? See our email flows & automation service or book a free audit.