30035: US A2P 10DLC - Message from a number still being configured

Twilio could not send your message because the sending number is still being configured for US A2P 10DLC. This happens when Twilio has received a request to register or deregister the number for an approved campaign, but the required Number Registration steps with ecosystem partners have not finished yet. You can send on A2P routes only after the number reaches the REGISTERED status.

• The number is in PENDING_REGISTRATION while Twilio completes Number Registration with ecosystem partners.
• The number is in PENDING_DEREGISTRATION after you removed it from a Messaging Service, moved it between campaigns, or made another change that triggered deregistration.
• You recently added, removed, or reassigned the number in a Messaging Service associated with a US A2P 10DLC campaign.
• You sent traffic before the number finished registration after campaign approval.
• You made repeated number assignment changes, which restarted Number Registration and extended processing time.

• Check the number's A2P registration status in Console and wait until the status is REGISTERED.
• Allow up to 24 hours for Number Registration or deregistration to complete. Processing time can vary based on registration volume across ecosystem partners.
• Do not remove and re-add the number to the Messaging Service in response to this error. That starts the registration process again and can delay activation further.
• Avoid moving numbers between Messaging Services, campaigns, or accounts unless the change is required. Each change can trigger a new deregistration or registration workflow.
• If the number has remained in a pending state for more than 24 hours, contact Support.

• Programmable Messaging and A2P 10DLC
• Troubleshooting A2P phone number registration issues
• A2P 10DLC Number Registration Best Practices