Errors Report in Single Notifications

Identify single notifications with sending failures for immediate analysis.

Here you can track individual notifications that encountered errors during sending, allowing identification of error patterns, focus on problem resolution, and improvement in send quality.

How to Access

Access: Marketing / Campaigns / Errors Report for Individual Notifications, as shown in the Figure 1:

^{Figure 1: Errors Report for Individual Notifications.}

---

Main Screen

^{Figure 2: Filter of the Errors Report for Individual Notifications.}

The main screen displays a table with all notifications that failed, organized in descending chronological order.

Error Counter

In the upper right corner of the screen there is a number indicating the total number of errors recorded in the filtered period.

In the example in Figure 2: 34 errors. This counter helps to get a quick view of the volume of failed sends.

Available Buttons

• Filters: Filters errors by period, service and API key

• Export: Exports the report in CSV or PDF format

---

Table Information

The errors table contains the following columns:

Column	Description
Description	Type of error that occurred
Service Icon	Visual indicator of the channel (SMS, WhatsApp, Email)
Date	Date and time when the error occurred
API Key	Technical identifier of the message (empty when not available)
Actions	Button to investigate error details

---

Types of Errors

Errors are described in the first column. The most common error found in the image is:

Bad Request

Meaning: Invalid or malformed request

Possible causes:

• Invalid or poorly formatted phone number

• Template with incorrect parameters

• Missing required data

• Problems in the structure of the API request

How to resolve:

1. Click the magnifying glass icon (Actions) to see details

2. Check the phone number format

3. Confirm that the template is correct

4. Validate all required parameters

---

Filter Errors

^{Figure 3: Available Filters.}

The button Filters allows refining the view of errors.

Filter Fields

Period:

• Start date field (format: DD/MM/YYYY HH:MM)

• End date field (format: DD/MM/YYYY HH:MM)

• Example in the image: 01/08/2026 00:00 to 01/15/2026 23:59

Sets the date range to view specific errors.

Service:

• Selection field

• Allows choosing the specific channel

• Options: SMS, WhatsApp, Email

• Example in the image: SMS selected

• Has button X to clear selection

API Key:

• Selection field

• Filters by specific technical identifier

• Useful when there is a technical reference for the error

How to Apply Filters

1. Click the button Filters

2. Set the desired period, service and/or API key

3. Click Filter to apply

4. Or click Cancel to close without applying

Results are updated according to the selected filters, and the error counter is updated.

---

Export Report

^{Figure 4: Export Report.}

The button Export allows generating reports of the errors for external analysis.

How to Export

1. Click the button Export

2. The system displays the user's login email by default, which can be changed

3. Choose the desired format:

   • CSV: For analysis in spreadsheets

   • PDF: For printing or presentation

4. Click Export to confirm

5. Or click Cancel to close

The file is sent to the configured address, including only the errors visible after applying filters.

Recommendation: Use CSV when you need to analyze large volumes of errors or perform statistical analyses in tools like Excel or Google Sheets.

---

Investigate Error Details

^{Figure 5: Investigation Icon.}

In the Actionscolumn, each error has a magnifying glass. By clicking it, you can access detailed information about that specific error.

Expected Information

When investigating an error, you may find:

• Phone number or recipient identifier

• Template used

• Parameters sent

• Full technical error message

• Exact error timestamp

• API error code

• Correction suggestions

---

Common Error Patterns

Bad Request - Invalid Number

Symptoms: Multiple errors Bad Request via SMS

Likely cause: Phone numbers with incorrect format

Solution:

1. Export the errors report

2. Identify the problematic numbers

3. Check format (should have 13 digits: 55 + area code + number with leading 9)

4. Fix in the database

5. Validate numbers before new sends

Bad Request - Incompatible Template

Symptoms: Errors concentrated in a specific template

Likely cause: Template with incorrect parameters or not approved

Solution:

1. Filter by specific period

2. Identify which template is causing problems

3. Review template in the system

4. Check approval with Meta/operator

5. Correct necessary parameters

Bad Request - Missing Data

Symptoms: Sporadic errors without a clear pattern

Likely cause: Required fields not filled

Solution:

1. Investigate specific error

2. Check which data is missing

3. Review data collection process

4. Implement validations before sending

---

Use Cases

Case 1: Daily Error Audit

Objective: Check all errors that occurred in the last 24 hours

Flow:

1. Access Errors Report for Individual Notifications

2. Set filter for the last 24 hours

3. Check the total error counter

4. Analyze patterns (same error, same service, same period)

5. Take corrective actions

Recommended frequency: Daily

Case 2: Identify Recurring Problem

Objective: Discover if there is a pattern in the errors

Flow:

1. Filter for a 7-day period

2. Export report in CSV

3. Open in a spreadsheet

4. Group by error type

5. Identify the most frequent

6. Investigate root cause

7. Implement permanent fix

Case 3: Validate Implemented Fix

Objective: Confirm that the problem has been resolved

Flow:

1. Identify the period before the fix

2. Note the number of errors

3. Implement the fix

4. Wait for an equivalent period

5. Compare the number of errors

6. Confirm reduction

Case 4: Report for Management

Objective: Document issues for presentation

Flow:

1. Filter the desired period (example: last month)

2. Export in PDF

3. Analyze main error types

4. Calculate the percentage over total sends

5. Prepare executive report

6. Present with actions taken

---

Difference between Reports

Errors Report for Individual Notifications

Location: Marketing / Campaigns / Errors Report for Individual Notifications

Displays: Only notifications that failed

When to use:

• Investigate specific problems

• Identify failure patterns

• Measure error rate

• Quality audit

Individual Notifications Report

Location: Marketing / Campaigns / Individual Notifications Report

Displays: All notifications (success and error)

When to use:

• Overview of sends

• Measure success rate

• Check specific deliveries

• Engagement analysis

• Management reports

Relationship between the Reports

The errors shown in this report also appear in the Individual Notifications Report, but there they are mixed with successes. This report provides exclusive focus on problems.