> For the complete documentation index, see [llms.txt](https://help.bots.business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bots.business/use-the-mobile-app/broadcasts.md).

# Monitor a broadcast

Inspect broadcast tasks, distinguish processed from delivered messages, and manage paused or failed broadcasts in Bots.Business.

Open your bot → **Broadcast** to inspect its broadcast tasks. This screen tracks existing work; the BJS [broadcasting guide](/bjs-reference/broadcasts.md) explains how to create that work.

Before a real broadcast, test the sending command in a controlled chat. Check the intended audience and the message content, especially links and formatting.

## Open task details

1. Find the task by its command, creation time, and status.
2. Choose **View details**.
3. Read **Audience** and **Delivery**, then check progress and recent updates.
4. Refresh before deciding whether the task has stopped progressing.

<figure><img src="https://3310729168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVh0yg9olT-QWqi3AYt%2Fuploads%2Fgit-blob-90947822bf2167894cd277e6248510457ad8dbdb%2Fmobile-broadcast-details.png?alt=media" alt="Audience and Delivery for a demonstration broadcast: 30 available recipients, 10 delivered, 2 failed and 18 pending"><figcaption><p>Audience and Delivery for a demonstration broadcast: 30 available recipients, 10 delivered, 2 failed and 18 pending</p></figcaption></figure>

## Understand the counters

| Counter              | What to look for                                                     |
| -------------------- | -------------------------------------------------------------------- |
| Available recipients | The audience currently counted for this task.                        |
| Blocked/excluded     | Chats not available under the task's eligibility rules.              |
| Processed            | Work already processed; this is not the same as successful delivery. |
| Delivered            | Reported successful deliveries.                                      |
| Failed / undelivered | Attempts that did not produce a successful delivery.                 |
| Pending              | Work still to be processed.                                          |

While the audience is being counted, the screen can show **Counting recipients**. Wait for the count before interpreting its totals. A completed task can still have failed deliveries: completion describes the task's progress, not universal delivery.

<figure><img src="https://3310729168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVh0yg9olT-QWqi3AYt%2Fuploads%2Fgit-blob-1f9540f123d7af24061d036b9d45d672e5f64d1c%2Fmobile-broadcast.png?alt=media" alt="A demonstration broadcast task showing progress and delivery information"><figcaption><p>A demonstration broadcast task showing progress and delivery information</p></figcaption></figure>

## Pause, resume, or remove a task

Use **Pause** or **Run** when the action is available for that task. Check its status again afterward. Review the task before deleting it; deletion is not a way to recall messages that were already delivered.

For a bulk deletion, inspect the selection and check the result for each task.

## Investigate failed delivery

Check whether the recipient blocked the bot, the chat is excluded, or Telegram rejected the message. Inspect **Errors** for related failures. Sending again without understanding the failure can waste [iterations](/account-and-resources/iterations.md) and duplicate messages for recipients who already received them.

If a task remains pending, check bot status, iteration availability, and the sending command's background context. See [background execution](/bjs-reference/background.md) and [performance troubleshooting](/troubleshooting/performance.md).