# 08 January: Broadcast - Retry Logic on Failure, activity log improvement, and more

### ⚙️ Improvements

#### **Broadcast - Retry logic on Failure**&#x20;

Error 131049 - Meta has restricted the user from sending the marketing template for a period. To resolve this, we can retry the failed template using the broadcast retry.

Broadcast retry consists of two types: smart retry and manual retry. Smart retry allows for automatic retries over a selected period of up to 7 days. In manual retry, the first retry can be scheduled 12 to 24 hours later, while the second and third retries can be set for 6 to 24 hours.

When using the Manual Retry option, we can schedule up to three retry attempts for failed messages. For a broadcast initially set for 10:30 AM on January 8th, the retries would be as follows:

\
1\. First retry: 24 hours later, on January 9th at 10:45 AM.\
2\. Second retry: 12 hours after that, on January 9th at 10:45 PM.\
3\. Third retry: another 12 hours later, on January 10th at 10:45 AM.

{% hint style="info" %}
For optimal results, we recommend allowing a minimum of three days to maximize retry attempts. If the last retry which is the third retry also fails, the retry status will be elapsed.
{% endhint %}

<figure><img src="/files/5tKSjjRgf6ITqsPInuxW" alt=""><figcaption></figcaption></figure>

#### **Activity Logs now records user-level active and inactive status**&#x20;

Changing the activity status by the user or admin creates entries in the Activity log to monitor user actions with Active and Inactive Status.

![QesttFMQAAAABJRU5ErkJggg==](/files/9mjhbB6dQfwJaXpdPZIc)

#### **Rich text editor similar to WhatsApp**&#x20;

The Conversation module now includes new formatting options: Monospace, Number List, Bullet List, and Block Quote. These options are also applicable to Canned Responses, and Bullet and Number List formats have been added to Template Messages.

For a numbered list, use 1. 2. 3. followed by a space. For bullet points, start a line with - followed by a space.

<figure><img src="/files/QlaKMI1IX1SD5RJk4huN" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changelog.gallabox.com/january-2025/08-january-broadcast-retry-logic-on-failure-activity-log-improvement-and-more.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
