Workflow Trigger - Messaging Error Code - SMS

Overview

The "Messaging Error - SMS" trigger allows you to initiate workflows automatically whenever a SMS has resulted in undelivered state and returned one of the below-mentioned error code.

Trigger Name

Messaging Error - SMS

Trigger Description

How to Configure

1. 1Choose a Workflow Trigger:
2. 2Workflow Trigger Name:
3. 3Filters:

Code | Description

30007 | Carrier Violation

30034 | A2P Registration Pending on Number |

30032 | Toll Free Number not Verified

30005 | User Inactive/Number does not exist

30003 | Unreachable/Out of Service Number

30004 | Do not want SMS/DND enabled

30006 | Landline/Incapable to receive SMS

30023 | US A2P 10DLC - Daily Message Cap Reached

21408 | Permission to Send SMS Not Enabled for 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 with STOP (Opted Out)

30011 | MMS Not Supported by Recipient Number or Region

30033 | A2P Campaign Suspended or Deleted

21661 | From' Number Is Not SMS-Capable

21635 | To' Number Cannot Be a Landline

30037 | Outbound Messaging Disabled

30002 | Sub-Account Suspended

Example

Let’s say you are running an SMS campaign to promote a new product, and you want to automatically remove contacts who have a high chance on not getting the messages next time or want to add a tag to re trigger them an SMS after sometime.some time

1. 1Choose a Workflow Trigger:
2. 2Workflow Trigger Name:
3. 3Filters:

Email Setup & Deliverability

47 step-by-step Adaptive AI guides in this section.

Before you begin

“Workflow Trigger - Messaging Error Code - SMS” is part of the Conversations → SMS area in Adaptive AI. Send, receive, track, and troubleshoot text messages. Automation changes can affect many records at once, so the safest approach is to define the intended entry condition, action, and stopping point before publishing anything. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Write down the exact trigger, filters, expected action, and condition that should stop or bypass the automation.
• Use an internal test contact with complete sample data, a valid communication channel, and consent appropriate to the test.
• Confirm that every connected account, custom field, pipeline, calendar, or template referenced by the automation still exists and is available.
• Record the current published status and settings so you can compare behavior or restore the earlier configuration if necessary.
• Choose a quiet test window when a controlled enrollment cannot interfere with active customer communication.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Save the configuration, review every branch from top to bottom, and publish only after required fields and warnings are resolved.
2. 2Run one controlled test using known inputs and note the exact time the test record entered the automation.
3. 3Open execution history and confirm that the record followed the expected branch in the correct order.
4. 4Verify the intended message, task, field update, or status change occurred once and contains the correct merged information.
5. 5Run a negative test that should not qualify; it should remain outside the automation without producing side effects.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm the automation is published and that the trigger filters match the test record exactly, including capitalization and date conditions.
• Review re-entry settings to determine whether the same record is allowed to enter again or is being correctly excluded.
• Check the first failed or skipped step in execution history instead of changing several steps at the same time.
• Verify wait steps, account time zone, business-hour windows, and scheduled-send rules when an action appears delayed.
• Reconnect or reauthorize any external service that reports an expired credential, missing scope, or unavailable resource.

Best practices

• Use names that state the audience, trigger, and outcome so another administrator can understand the automation without opening it.
• Keep entry filters narrow and add explicit stop conditions to prevent duplicate messages, tasks, or opportunity changes.
• Respect contact consent, do-not-disturb status, quiet hours, and channel-specific opt-out requirements in every communication path.
• Change one behavior at a time, test it, and document the result before expanding the automation to more records.
• Review execution errors and unexpected enrollments after launch, then again after any connected integration or template changes.