> ## Documentation Index
> Fetch the complete documentation index at: https://docs.growthxai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Stalled and Running-Dry Alerts

> The platform tells you when a sequence quietly stops sending, or when a sender is about to run out of leads.

A campaign that stops sending is worse than one that performs badly, because nobody notices. The platform watches for two situations and raises an alert on its own. You don't have to go looking.

## Sequence stalled

A sequence is **stalled** when all of this is true:

* It is **active** and has live enrollments.
* At least one lead should be producing an action right now — it isn't in a delay, isn't waiting for an invitation to be accepted, and isn't waiting for a person.
* **Nothing was sent** in the last 26 hours, and **nothing is planned** for the next 26 hours.
* At least one sender in the pool actually had working hours yesterday or today.

That last condition matters: a pool whose senders don't work at weekends is not stalled on a Sunday.

## Sender running dry

A sender in an active sequence has **fewer than 2 days** of new leads left, measured as leads with no outbound step yet, divided by its current daily invitation allowance.

The alert clears on its own once the sender is back above 3 days, so topping up doesn't leave a stale warning behind.

## What happens when one fires

| Where              | What you see                                                                                                  |
| ------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Dashboard**      | The alert joins **Needs attention** with the reason and a link                                                |
| **Sequences list** | A **stalled** badge on the sequence                                                                           |
| **Sender page**    | A running-dry notice with **Enrol more leads** and **Add an auto-enrol rule**                                 |
| **Email**          | Owners and managers are emailed, plus any [alert recipients](/senders/sender-profiles#settings) on the sender |
| **Webhook**        | `sequence.stalled` or `sender.running_dry` fires. `sequence.recovered` fires when it clears.                  |

Each alert is raised **once per occurrence**. It resolves by itself when the cause goes away, and only fires again if the problem comes back. There is no dismiss button, because a dismissed alert would hide a real problem.

## Why isn't this sending?

You don't have to wait for an alert. Two buttons run the same diagnosis on demand:

* **Why isn't this sending?** on the sequence top bar
* The same button on a sender's page

It checks senders, caps, schedules, health and lead supply, and answers in plain words: one **reason**, then each cause with a **what to do next**. Claude answers the same question with the same diagnosis when you ask "why isn't anything sending?".

## Common causes and fixes

| Reason                                               | Fix                                                                                              |
| ---------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| Every pool sender is paused or needs to log in again | [Reconnect or resume the sender](/senders/sender-profiles#reconnecting)                          |
| Daily caps are already used up                       | Nothing to do. Sending resumes tomorrow.                                                         |
| Outside working hours for every sender in the pool   | [Widen the schedule](/senders/senders-schedule-explained), or accept the pace                    |
| No eligible leads left                               | Enrol more, or add an [auto-enrol rule](/sequences/creating-managing-sequences/auto-enrol-rules) |
| Health below 50                                      | The sender is auto-paused. See [Sender health](/deep-dive/understanding-sender-health).          |
| Every live lead has replied                          | Working as intended: the sequence has done its job                                               |

## Related articles

* [My Sequence Is Stuck — Troubleshooting Checklist](/sequences/sequence-troubleshooting/sequence-is-stuck-checklist)
* [Auto-Enrol Rules](/sequences/creating-managing-sequences/auto-enrol-rules)
* [Outbound Webhooks](/integrations-api/outbound-webhooks)