SMSs not leaving MKT_DATA_CORR_SMS table
For multiple Campaigns, unable to send SMSs to the Short Message Service Center (SMSC).
A campaign is executed with a volume of 80K users. Between 51K, the first 10K SMSs return to the outbound table with a Failed status and an error message displays.
On changing the status from Failed to null to resend the SMSs to the SMSC, the agent again picks the SMS from the MKT_DATA_CORR_SMS table. However, the record returns to the table with no error message.
Failed to connect to SMSC for Account - Name:[SMSC_LA_ACC], Type:[Notify].
Steps to Reproduce
- Run a Campaign. The campaign delivered a part of the SMSs. However, some of the SMSs are in the Failed status.
- Modify the record's status from MKT_DATA_CORR_SMS table to null such that the agent can pick the records again and send them to SMSC. The records return to the table without an error message.
A defect or configuration issue in the operating environment.
The records are not processed because the batch dataset, for the corresponding offerClassName column, for the SMS record is not present anymore.
Perform the following local-change to recover the failed records and re-add them for processing:
Set both the Status and retryattempts in the MKT_DATA_CORR_SMS table to null.
Published December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.