Red Triangle: Errors in campaigns and conversations
In the Campaigns Module:
You can view campaign sending errors by downloading thefailedones from the Campaigns panel. To do this, you can click on the red number in the "Failed" column:
Errors in sending messages from the conversations module can be viewed as a "tooltip" if you hover the cursor over the red triangle.
In conversations:
Below we share a list of possible errors when a Red Triangle appears in conversations, the cause, and how you can resolve them:
👇 Scroll down to see all possible errors
To learn more abouterror 131049,you can read the following article.
Other specific Campaign errors
There are certain infrequent errors in Campaigns that require additional investigation. In those situations, if the recommended solution does not resolve the issue, please contact the support team.
👇 Scroll down to see all possible errors
If you want to see the complete error file, clickhere
📊 How to estimate the impact of the red triangle error on my campaigns?
Thered triangleindicates that there was a failure in the execution of the flow, but currentlythere is no direct metricthat quantifies it in the reporting. However, it is possible to make a reasonable estimate by following these steps:
🧭 Step by step to estimate the impact:
Download the campaign auditGo to the Reports module, Outbound (campaigns) sectionSelect the campaign you want to analyzeUse theExport auditoption to obtain the file with the interaction records.
Download the campaign audit
Go to the Reports module, Outbound (campaigns) section
Go to the Reports module, Outbound (campaigns) section
Select the campaign you want to analyze
Select the campaign you want to analyze
Use theExport auditoption to obtain the file with the interaction records.
Use theExport auditoption to obtain the file with the interaction records.
Filter unanswered conversationsIn the downloaded file, filter those conversations thatdid not register a user response after receiving the template.A useful indicator isinactivity greater than 10 minutesafter the first message without continuity.
Filter unanswered conversations
In the downloaded file, filter those conversations thatdid not register a user response after receiving the template.
In the downloaded file, filter those conversations thatdid not register a user response after receiving the template.
A useful indicator isinactivity greater than 10 minutesafter the first message without continuity.
A useful indicator isinactivity greater than 10 minutesafter the first message without continuity.
Review the execution of the flowThese conversations are usually stopped by an error in the flow piece (for example, misconfigured button, missing evaluator, or poorly connected piece).Checkif, after not receiving a response, the flow took an unwanted path orcontinued requesting unnecessary information(such as asking for data from users who had already rejected the proposal).
Review the execution of the flow
These conversations are usually stopped by an error in the flow piece (for example, misconfigured button, missing evaluator, or poorly connected piece).
These conversations are usually stopped by an error in the flow piece (for example, misconfigured button, missing evaluator, or poorly connected piece).
Checkif, after not receiving a response, the flow took an unwanted path orcontinued requesting unnecessary information(such as asking for data from users who had already rejected the proposal).
Checkif, after not receiving a response, the flow took an unwanted path orcontinued requesting unnecessary information(such as asking for data from users who had already rejected the proposal).
Document the difference between sends and responsesThe gap between delivered templates and users who continued the conversation can give you anestimation of the impact of the error.
Document the difference between sends and responses
The gap between delivered templates and users who continued the conversation can give you anestimation of the impact of the error.
The gap between delivered templates and users who continued the conversation can give you anestimation of the impact of the error.
⚠️ Important: check your flows for frequent errors
Some errors not only interrupt the conversation, but can lead toinvasive experiencesif the user has already expressed disinterest and the bot continues to interact.
Some errors not only interrupt the conversation, but can lead toinvasive experiencesif the user has already expressed disinterest and the bot continues to interact.
This type of situationscan be penalized by Meta, as they violate recently reinforced anti-spam policies.
This type of situationscan be penalized by Meta, as they violate recently reinforced anti-spam policies.
✅ Key recommendations
Carefully review the routes of the conversational flowto prevent the bot from insisting or misinterpreting negative responses.
Carefully review the routes of the conversational flowto prevent the bot from insisting or misinterpreting negative responses.
Incorporatedfallback messages and clear conditionsto stop the conversation when the user does not interact or rejects the proposal.
Incorporatedfallback messages and clear conditionsto stop the conversation when the user does not interact or rejects the proposal.
Simulate different scenarios before publishing: rejection, silence, partial clicks, validation errors.
Simulate different scenarios before publishing: rejection, silence, partial clicks, validation errors.