Engineering Atlas
☰ Menu
PortfolioAtlasDeploySQLData ViewsEnvBites
PT
Engineering Atlas / Snippets / Held / Undeliverable Mobile Numbers
sfmc // MobileConnectPRODUCTION

Held / Undeliverable Mobile Numbers

Inspect MobileConnect numbers that are held after repeated delivery failures.

sqlsmsundeliverablebounce
Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources1Other sources0Last verified2026-10-05

Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.

EvidencePRODUCTION
Difficultyfoundation
Verified2026-10-05
Use when

SMS delivery failures.

Cleaning a mobile audience before repeated sends.

SELECT
    MobileNumber,
    Undeliverable,
    BounceCount,
    FirstBounceDate,
    HoldDate
FROM _UndeliverableSMS
WHERE Undeliverable = 1
Why it works

_UndeliverableSMS exposes the held flag, bounce count, first bounce and hold date for the mobile number.

Connected knowledge

Keep following the context.

Explicit and inferred relationships from the Atlas model.

View this node in graph →
RecipeDIRECT LINK
SMS Delivery & Opt-Out Diagnostic

Trace MobileConnect send state, delivery semantics, held numbers and subscription events without treating one status field as the whole truth.

Recipe step
Data View
_UndeliverableSMS

Current MobileConnect held/undeliverable mobile-number state and bounce history.

_UndeliverableSMS referenced in snippet
Data View
_SMSMessageTracking

MobileConnect SMS send/receive tracking, delivery-status context and Journey identifiers.

Shared context: mobileconnect
Data View
_SMSSubscriptionLog

MobileConnect subscription history by mobile number/keyword, including opt-in and opt-out state.

Shared context: mobileconnect
Snippet
SMS Tracking by Journey Version

Map Journey-sent SMS tracking records to the Journey version via JBDefinitionID.

Shared context: mobileconnect
Snippet
Recent MobileConnect Opt-Outs

Review recently logged SMS opt-outs without assuming every row has a SubscriberKey.

Shared context: mobileconnect
Runbook
MobileConnect / Journey SMS Troubleshooting

Trace an SMS from account configuration and consent through Journey execution, tracking status and held-number state.

Shared context: mobileconnect
Production Bite
A STOP Can Exist Without a SubscriberID

You see an opt-out/subscription event for a mobile number but no corresponding contact/subscriber ID.

Shared context: mobileconnect
Sources / verification
Salesforce — Undeliverable SMS ↗