Product Agents now tell you when a Klaviyo flow can't send
A Klaviyo flow that is a draft, manual-only, or archived cannot send. Any agent attached to one is now flagged in the dashboard, with the exact situation named and the fix spelled out. Agents with working flows behave exactly as before.
A flow can exist in Klaviyo and still be switched off: saved as a draft, set to manual-only so it only sends when someone triggers it by hand, or archived. Until now we only checked that the flow was there, so an agent could look perfectly healthy in your dashboard while nothing ever went out. Usually the first sign something was wrong was you wondering why you had no sends.
What you see now
Any agent whose flow can’t send is flagged clearly, and the dashboard tells you exactly which situation you’re in and what to do:
- A draft flow says to publish it in Klaviyo.
- A manual-only flow says to set it to send automatically.
- An archived flow says to unarchive it.
Why naming the situation matters
That last part matters more than it sounds. Before, anything that wasn’t live was described as a draft, so if you had a manual-only or archived flow you went hunting for a Publish button that doesn’t exist for you.
Nothing changes if your agents are sending
Agents with working flows behave exactly as before, and nothing has changed about how messages are generated or sent. If your agents are already sending, there’s nothing for you to do.