Skip to content
A2PCheck

Twilio Error 30035: Number Still Being Configured (A2P 10DLC)

Error 30035 is the "almost registered" state: the campaign exists but the number is still being wired up with carrier partners, so sends are held.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

What Twilio error 30035 means

The sending number can't transmit because it is still in configuration for US A2P 10DLC — its registration with downstream ecosystem partners hasn't finished. The number typically shows a PENDING_REGISTRATION (or PENDING_DEREGISTRATION) status.

Official Twilio name: 30035: US A2P 10DLC - Message from a Number Still Being Configured A2P 10DLC-specific

Why error 30035 happens

You sent traffic before registration completed, or the number was recently added, removed, or reassigned between Messaging Services or campaigns — each reassignment restarts the registration clock. Repeatedly moving a number keeps it stuck in the configuring state.

How to fix error 30035

  1. Check the number's A2P registration status in the Console and wait until it reads REGISTERED before sending production traffic.
  2. Allow up to 24 hours for provisioning to complete after registration or a Sender Pool change.
  3. Do NOT remove and re-add the number — that restarts the registration process and prolongs 30035.
  4. Avoid moving numbers between Messaging Services or campaigns while registration is in flight.
  5. If the status is still pending after 24 hours, contact Twilio Support with the number and campaign details.

Related error codes

Twilio error 30034: US A2P 10DLC - Message from an Unregistered NumberA2P 10DLC & toll-free registrationTwilio error 30024: Numeric Sender ID Not Provisioned on CarrierA2P 10DLC & toll-free registrationTwilio error 30022: US A2P 10DLC - Rate Limits ExceededThroughput & daily caps

Official reference

For the authoritative definition and any changes to this code, see the Twilioerror catalog. A2PCheck is an independent pre-scan layer for the campaign packet you submit — it can't change carrier behavior.

Twilio error 30035 documentation

Frequently asked questions

What's the difference between 30034 and 30035?

30034 means the number isn't associated with an approved campaign at all (unregistered). 30035 means registration is underway but not finished — the number is still being configured with carrier partners. 30035 usually clears on its own once provisioning completes.

Why did 30035 come back after I moved my number?

Removing and re-adding a number, or moving it between Messaging Services or campaigns, restarts the registration process. Leave the number in place and wait for the REGISTERED status instead of reassigning it.

Free — no signup required

Catch the campaign issue behind this error before you resend

Many of these errors trace back to an unregistered, mis-scoped, or non-compliant A2P 10DLC campaign. Paste your campaign details for a free readiness scan — no signup.

Independent pre-submission check
No Twilio or TCR submission
Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

01

Campaign Info

Basic details about your messaging campaign.

0 characters — Too short — describe who opts in, what you send, and how often.

02

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages
03

Opt-In / Message Flow

How users consent to receive your messages.

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

  • Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
  • Spell out the consent language — what the subscriber explicitly agrees to.
  • State the message frequency (e.g. recurring, varies, msgs/month).
  • Include a "Message and data rates may apply" disclosure.
  • Link a privacy policy describing how you handle subscriber data.
  • Clarify that consent isn't a condition of purchase, where that applies.
  • Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan
Scan my campaign for this issueAll A2P 10DLC error codes