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 | Error Description | Retryable? |
| 1001 | Campaign could not be added/removed due to an error. We are working with our peer to remediate. Please retry after 2-3 business days. (error #1001). | Yes, after 2-3 business days |
| 1002 | Carrier API error. Contact TCR to confirm Content Provider creation on T-Mobile. Then retry (error #1002). | Yes, after contacting TCR |
| 1003 | Campaign could not be added/removed due to an error. We are working with our peer to remediate. Please retry after 2-3 business days. (error #1003). | Yes, after 2-3 business days |
| 1004 | Please review this number as it seems to belong to another provider. If you think this is an error please contact Bandwidth support and provide proof of ownership and authorization to text enable the number (error #1004). | No |
| 1005 | The maximum allowed phone numbers on campaign is 49. Please apply for a Sub-ID (error #1005). | No |
| 1006 | Error while adding/deleting campaign ID. Please try again (error #1006). | Yes |
| 1007 | Please verify and fix 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 (error #1007). | Must be corrected |
| 1008 | There was an error processing the request. Please verify the request details and retry (error #1008). | Yes |
| 1009 | Timed out waiting for response from the downstream partner. Please try again (error #1009). | Yes |
| 1010 | The TN could not be deprovisioned from a campaign because the campaign is not deployed. Please contact Bandwidth support to remediate (error #1010). | No |
| 1011 | The TN could not be provisioned to a campaign because the campaign is not completely ready yet in the downstream partner's system. Please contact Bandwidth support to remediate (error #1011). | No |
| 1012 | The campaign could not be added/removed from the TN as the campaign is in the suspended state. Please select an active campaign (error #1012). | No |
| 1013 | The maximum allowed phone numbers on campaign is 49. Please apply for a Sub-ID (error #1013). | No |
| 1014 | Previous order with the similar request was already completed. This request is not needed (error #1014). | No |
| 1015 | Our downstream partner could not de-provision a TN because it is not associated with the campaign. Please contact Bandwidth support to resolve with our downstream partner (error #1015). | No |
| 1016 | Timed out waiting for the downstream partner to accept the request. Please try again (error #1016). | Yes |
| 1018 | The TN could not be provisioned because the campaign is has been blocked by our downstream partner. Please contact Bandwidth support to resolve with our downstream partner (error #1018). | No |
| 1019 | The TN could not be provisioned because it is already associated to another campaign. Please correct and resubmit or contact Bandwidth support if you feel this is in error (error #1019). | Must be corrected |
| 1020 | The TN could not be correctly provisioned due to a downstream partner error. Please contact Bandwidth support to remediate (error #1020) | No |
| 1021 | The TN could not be provisioned because the campaign is a SOLE_PROPRIETOR campaign and the maximum amount of long codes allowed is 1. Please correct and resubmit or contact Bandwidth support if you feel this is in error (error #1021). | Must be corrected |
| 1022 | The TN could not be provisioned because the campaign is in the process of being suspended. Please correct and resubmit or contact Bandwidth support if you feel this is in error (error #1022). | Must be corrected |
| 1023 | Campaign could not be added/removed due to an error from downstream partner which requires manual work from them. Please contact Bandwidth support to resolve with our downstream partner (error #1023). | No |
| 1024 | The request could not be completed as the downstream partner is still processing a previous transaction. Please wait for that transaction to complete before retrying (error #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 resolve with our downstream partner (error #1025). | Yes |
| 1026 | The TN could not be provisioned because per the downstream partner, the TN is not owned by the customer or the NNID is not authorized to be used. Please verify ownership of the TN or verify the NNID submitted in the request and try again. (error #1026). | Must be corrected |
|
1030 (or 1017) |
The request will not be processed because the TN has been provisioned an excessive number of times in this calendar week. Please verify that automation is only provisioning as needed. (error #1030) | No |
|
1031 |
Unable to complete provisioning (all retries exhausted). Please retry after 2-3 business days (error #1031). | Yes, after 2-3 business days |
| 1211 | LOA is required from the Number Provider XXXXXX (error #1211). Please contact Bandwidth support with the LOA. | No |
| 1212 | Not allowed to provision Mobile numbers (error #1212). | No |
| 1214 | Not allowed to provision property-value campaign_id=CXXXXXX (error #1214). | No |
| 9999 | The request could not be processed due to an unknown error from our downstream partner. Please contact Bandwidth support to begin investigation internally (error #9999). | No |
Article is closed for comments.