📲 Expanded Message Error Handling in Workflows

We’ve enhanced 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 improvement leads to better automation, cleaner contact lists, and fewer manual tasks when a message fails to send.

The trigger now supports an expanded range of carrier error codes, including:

• 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: Sub-account suspended

1. Filter triggers by specific error codes

2. Use If/Else branches to tailor 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. Improve automation for both Native Phone and Carrier-connected numbers

This gives you:

• Improved message deliverability and contact quality

• Fewer wasted sends to unreachable or non-compliant numbers

• Greater control over how your system responds to actual delivery failures

• Reduced dependency on support teams for error triage

• MMS-specific error code 30011 is now included for proactive failure handling

• Error code 30008 (Unknown) can be broad—use workflow actions with caution

• Codes like 30023 reset daily, so avoid permanent contact suppression for these

This feature was developed based on your feedback, especially from teams managing high-volume messaging and contact hygiene. We hope it provides you with more control, less guesswork, and smarter automations.