30901: Campaign rejection - The campaign registration request timed out.
MESSAGING
ERROR
Your A2P 10DLC campaign registration request timed out before the review workflow completed. This usually means the campaign stayed under review too long or another party in the registration process did not return a decision within the expected service window. Check the current state in Console or by fetching the UsAppToPerson resource and reviewing campaign_status.
- The campaign review did not complete before the request timed out.
- A third party involved in A2P 10DLC registration did not respond within the expected service window.
- The campaign required additional review because the use case, campaign description, sample messages, message flow, opt-in or opt-out details, website, or brand information was incomplete, unclear, or inconsistent.
- The campaign was still in
PENDINGorIN_PROGRESSwhen the request timed out.
- Check the campaign in Messaging > Regulatory Compliance > Campaigns or fetch the
UsAppToPersonresource. Ifcampaign_statusisFAILED, review theerrorslist to identify the rejected fields and correct them before you resubmit. - Review the campaign before you resubmit it. Make sure the selected use case matches your actual traffic and that the campaign description, sample messages, message flow, opt-in process, website, and brand details are complete and consistent.
- If the campaign can be edited, update the existing failed campaign and resubmit it for approval instead of deleting it. Twilio allows repeated resubmissions, and the vetting fee is assessed only once per campaign.
- Delete and recreate the campaign only when the selected use case is wrong or the failure is tied to the associated brand rather than the campaign details.
- If the campaign remains pending beyond the current review window or repeated submissions continue to time out, contact Support with your account details, Messaging Service SID, and campaign information.