SuprSend workflow never fires: case, distinct_id, or Draft state
Shows how to fix suprSend workflow never fires: case, distinct_id, or Draft state. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
When a SuprSend event goes in but nothing comes out, check three things in order: the event name casing matches the trigger exactly, the user's distinct_id already exists in SuprSend (unknown users' events are dropped silently), and the workflow is committed, not still in Draft.
Steps
- When a SuprSend event goes in but nothing comes out, check three things in order: the event name casing matches the trigger exactly, the user's distinct_id already exists in SuprSend (unknown users' events are dropped silently), and the workflow is committed, not still in Draft. Any one of these produces zero errors and zero notifications.
When to use
You are seeing this: When a SuprSend event goes in but nothing comes out, check three things in order: the event name casing matches the trigger exactly, the user's distinctid already exists in SuprSend (unknown users' events are dropped silently), and the workflow is... Use this skill when you run into "SuprSend workflow never fires: case, distinctid, or Draft state".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.