Overview
We’ve improved the "Messaging Error – SMS" workflow trigger to allow you to take action on a broader range of failed message scenarios, including both SMS and MMS.
This enhancement means better automation, cleaner contact lists, and fewer manual tasks when a message fails to send.
What’s New?
The trigger now accommodates many more carrier error codes, including:
New error types you can now act on:
-30023
: Daily message cap reached (US A2P)
- 21408
: SMS not permitted to this region
- 30008
: Unknown error
- 21606
: Invalid "From" phone number
- 21211
: Invalid "To" phone number
- 21614
: "To" number is not a valid mobile number
- 21610
: User replied STOP (opt-out)
- 30011
: MMS not supported by recipient or region
- 30033
: A2P campaign suspended or deleted
- 21661
: "From" number is not SMS-capable
- 21635
: "To" number is a landline
- 30037
: Outbound messaging disabled
- 30002
: Account suspended
Previously Supported Codes:
30007
, 30034
, 30032
, 30005
, 30003
, 30004
, 30006
What You Can Do Now
1. Filter triggers by specific error codes
2. Use If/Else branches to customize follow-up actions (e.g., tag contact, notify team, update custom fields)
3. Automate smart list hygiene, such as skipping retries or flagging invalid numbers
4. Enhance automation for both Native Phone and Carrier-connected numbers
Why It Matters
This gives you:
• Better message deliverability and contact quality
• Fewer wasted sends to unreachable or non-compliant numbers
• More control over how your system responds to real-world delivery failures
• Reduced reliance on support teams for error triage
Good to Know
• The MMS-specific error code 30011
is now included for proactive failure handling
• Error code 30008
(Unknown) can be broad — use workflow actions cautiously
• Codes like 30023
reset daily, so avoid permanent contact suppression for these
This feature was shaped by your feedback — particularly from teams managing high-volume messaging and contact hygiene. We hope it gives you more control, less guesswork, and smarter automations.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article