Why a Workflow Can Create a Message Without Sending It
Last updated: April 12, 2026
Last Updated: April 12, 2026
Customer-Facing Guide
Start Here
A workflow can sometimes create the message record but still fail to send the message. That usually means the automation got part of the way through the process, but a required sending condition was missing or not yet satisfied.
The most common reasons
The sending number was missing or set incorrectly.
The workflow step had incomplete or invalid input.
The message was waiting on sending hours or timing rules.
The contact entered too late for the intended reminder window.
Required assignment or personalization data was not ready yet when the step fired.
A useful way to think about it
| Stage | What can go wrong |
|---|---|
| Trigger fired | The automation started, but later fields were missing or not ready. |
| Message step created | The message exists, but the workflow did not have a usable sending number. |
| Timing / eligibility | The send step was not actually eligible yet or missed the intended window. |
| Final send | The message tried to send and then failed for a delivery/configuration reason. |
What to check first
Confirm the correct sending number is selected in the workflow step.
Confirm the contact had the required data/assignment before the send step ran.
Review sending hours, delays, and reminder timing rules.
Check whether the contact entered the workflow too late for the message to be eligible.
Common example
A reminder workflow can look “broken” when a contact books inside the reminder window. In that case, the reminder step often never becomes eligible — not because Sendblue failed, but because the timing rule was never met.