10DLC provisioning errors
Emily Champion
After registering your campaigns with The Campaign Registry (TCR), there's an additional step that Bandwidth takes on your behalf to register your traffic fully within the industry. When there are errors with this last provisioning step, you may see some failures in the telephone number (TN) option orders when you assign a TN to a campaign. The table below outlines the errors and actions you can take. If you were unable to resolve the error using the recommended actions, please open a ticket with the Bandwidth Support Team.
Note: If you are using the API to submit and check TN option orders, since the TnOptions order is asynchronous, it is recommended to create a tnoptions subscription to receive order status webhooks. Otherwise, you need to poll accounts/{accountId}/tnOptions/{orderId} to get the order status. If you are not using the API for TN option orders, you can check the status of your orders in the Bandwidth App by following the instructions in this article. With either method, please ensure you are paying attention to the status of your orders so you will know if your TN is fully provisioned or if there is an error you need to address.
| Error Number | New Error Description | Retryable? |
| 1001 | The campaign could not be added/removed due to an error. We are working with our downstream partner to remediate. Please retry after 2-3 business days. (A2P #1001) | Yes, after 2-3 business days |
| 1002 |
TCR encountered an error when trying to push your brand details to T-Mobile which is preventing campaigns from being attached to your brand. Please reach out to TCR or Bandwidth support to remediate. (A2P #1002) |
Yes, after contacting TCR |
| 1004 |
Please review this number as it seems to belong to another provider. If you believe you are receiving this message in error, please contact Bandwidth support and provide proof of ownership and authorization to enable this number for Messaging. (A2P #1004) |
No |
| 1005 | The maximum allowed phone numbers on a campaign without a Number Pool is 49. Please apply for a Number Pool. (A2P #1005) | No |
| 1006 |
We encountered an error while adding/deleting the Campaign ID. Please try again. (A2P #1006) |
Yes |
| 1007 | Please verify and correct the following fields in TCR, then retry: name <= 50 chars, contentprovider-name <= 50 chars, campaign-overview <= 4000 chars, messaging-flow <= 4000 chars, help-message <= 4000 chars, description <= 4000 chars, address <= 255 chars. (A2P #1007) | Must be corrected |
| 1008 | There was an error processing your request. Please verify your request details and retry. (A2P #1008) | Yes |
| 1009 | The request timed out waiting for a response from our downstream partner. Please try again. (A2P #1009) | Yes |
| 1010 | The TN could not be deprovisioned from the campaign because the campaign is not deployed. Please contact Bandwidth support to remediate. (A2P #1010) | No |
| 1011 | The TN could not be provisioned to a campaign because the campaign is not yet ready in the downstream partner's system. Please contact Bandwidth support to remediate. (A2P #1011) | No |
| 1012 | The TN could not be provisioned to a campaign because the campaign is suspended. Please select an active campaign. (A2P #1012) | No |
| 1014 | A previous order with a similar request was already completed. This request is not needed. (A2P #1014) | No |
| 1015 | Our downstream partner could not de-provision a TN because it is not associated with this campaign. Please contact Bandwidth support to resolve with our downstream partner. (A2P #1015) | No |
| 1018 |
The TN could not be provisioned because the campaign has been blocked by our downstream partner. Please contact Bandwidth support to remediate. (A2P #1018) |
No |
| 1019 |
The TN could not be provisioned because it is associated with another campaign. Please correct and resubmit or contact Bandwidth support if you believe you have received this message in error. (A2P #1019) |
Must be corrected |
| 1020 |
The TN could not be successfully provisioned due to a downstream partner error. Please contact Bandwidth support to remediate. (A2P #1020) |
No |
| 1021 |
The TN could not be provisioned because the maximum number of TNs permitted for a SOLE_PROPRIETOR campaign is 1. Please correct and resubmit or contact Bandwidth support if you believe you have received this message in error. (A2P #1021) |
Must be corrected |
| 1022 |
The TN could not be provisioned because this campaign is in the process of being suspended. Please correct and resubmit or contact Bandwidth support if you believe you have received this message in error. (A2P #1022) |
Must be corrected |
| 1023 |
The campaign could not be added/removed due to an error from a downstream partner which requires manual work from them. Please contact Bandwidth support to remediate. (A2P #1023) |
No |
| 1024 |
The request could not be completed as a downstream partner is still processing a previous order. Please wait for your outstanding orders to complete before retrying. (A2P #1024) |
Yes |
| 1025 |
There is a data mismatch between the request and the downstream partner's system. We will attempt to fix it. Please resubmit the request and if the issue persists, contact Bandwidth support to remediate with our downstream partner. (A2P #1025) |
Yes |
| 1026 |
Our downstream partner reports that this TN is not owned by the customer, or the NNID is not authorized for use, thus the TN could not be provisioned. Please verify ownership of the TN and verify the NNID submitted in the request before trying again. (A2P #1026) |
Must be corrected |
| 1027 |
The TN could not be provisioned because a downstream partner has failed to deploy the campaign. Please contact Bandwidth support to remediate. (A2P #1027) |
No |
| 1029 |
The TN could not be provisioned because the campaign has expired. (A2P #1029) |
No |
|
1030 |
Your request will not be processed because this TN has been provisioned an excessive number of times in the last 7 days. Please verify that any automations are only provisioning as needed. (A2P #1030) |
No |
|
1031 |
Unable to complete provisioning (all retries exhausted). Please retry after 2-3 business days. (A2P #1031) |
Yes, after 2-3 business days |
|
1032 |
Your request will not be processed because this TN has been provisioned an excessive number of times in the last 7 days. This number is already in the desired provisioning state. Please verify that any automations are only provisioning as needed. (A2P #1032) |
Requires review |
|
1033 |
The TN could not be provisioned because the campaign or brand associated with this campaign cannot be validated with TCR. Please verify that the campaign is not suspended, expired, or in another invalid state. (A2P #1033) |
No |
|
1034 |
The TN could not be provisioned because an LOA is required for the provider. Please contact Bandwidth support to remediate. (A2P #1034) |
No |
|
1035 |
The TN could not be provisioned because of an issue with the TN. This cannot be retried; please contact Bandwidth support to remediate. (A2P #1035) | No |
|
1036 |
The TN could not be provisioned because it is assigned to another provider. Please contact Bandwidth support if you believe you have received this message in error. (A2P #1036) | No |
|
1037 |
The TN cannot be provisioned because it is a toll-free number. (A2P #1037) | No |
|
1038 |
This TN cannot be provisioned because a different provider owns it and has not relinquished it to Bandwidth. Please contact Bandwidth support to remediate. (A2P #1038) | No |
|
1039 |
The TN cannot be provisioned because the campaign’s CSP ID is different from the CSP ID associated with the account that owns the TN. (A2P #1039) | No |
|
1040 |
The TN cannot be provisioned to the campaign because the campaign is not managed by Bandwidth. Please contact Bandwidth support if you believe you have received this message in error. (A2P #1040) | No |
| 9999 | The request could not be processed due to an unknown error from our downstream partner. We are working with them to remediate. Please retry after 2-3 business days. (A2P #9999) | Yes, after 2-3 business days |
Article is closed for comments.