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

# No sending channel connected

> Your agent is not sending. Work through the causes in order: no channel, outreach paused, a sender in error, a limit of zero, a resting day.

export const UiPath = ({children}) => {
  const parts = String(children).split(/\s*(?:→|>)\s*/).filter(Boolean);
  return <span className="pl-path">
      {parts.map((part, index) => <span key={`${index}-${part}`}>
          {index > 0 && <span className="pl-path__sep">→</span>}
          {part}
        </span>)}
    </span>;
};

export const Screenshot = ({id, alt, caption, frame = 'browser', url, marks = [], lang = 'en', workspace = 'northwind-outbound'}) => {
  const src = `/images/screenshots/${lang}/${id}.png`;
  const chrome = url ? `app.pipelime.ai/${workspace}${url}` : 'app.pipelime.ai';
  return <figure className={`pl-shot pl-shot--${frame} not-prose`}>
      <div className="pl-shot__frame">
        {frame !== 'bare' && <div className="pl-shot__bar">
            <span className="pl-shot__dots">
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
              <span className="pl-shot__dot" />
            </span>
            <span className="pl-shot__url">{chrome}</span>
          </div>}
        <div className="pl-shot__media">
          <img src={src} alt={alt} loading="lazy" />
          {marks.map(mark => <span key={mark.n} className="pl-shot__mark" style={{
    left: `${mark.x}%`,
    top: `${mark.y}%`
  }} aria-hidden="true">
              {mark.n}
            </span>)}
        </div>
      </div>
      {caption && <figcaption className="pl-shot__caption">{caption}</figcaption>}
    </figure>;
};

When an agent stops sending, the cause is almost always one of five things, and checking them in this order gets you to the right one fastest.

<div className="pl-availability">
  <div className="pl-availability__row">
    <div className="pl-availability__label">Where</div>
    <div className="pl-availability__value"><span className="pl-path">Outreach<span className="pl-path__sep">→</span>AI Agents</span></div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">Your role needs</div>
    <div className="pl-availability__value">Read access to AI Agents <code>read-campaigns</code>. Admin, Member and Viewer have it by default.</div>
  </div>

  <div className="pl-availability__row">
    <div className="pl-availability__label">To create or change</div>
    <div className="pl-availability__value"><code>create-campaigns</code> to add one, <code>update-campaigns</code> to change one, on top of the permission above.</div>
  </div>

  <div className="pl-availability__note">If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.</div>
</div>

## Where to look

Two screens carry every signal here. Open the agent from <UiPath>Outreach → AI Agents</UiPath> and stay on its **Dashboard** tab: the banner strip is at the top of it, and the **Sending limits** card is lower down, in the narrow right-hand column (on a narrow screen everything stacks into one). For anything about one specific mailbox, open <UiPath>Integrations → Integrations → Email Accounts</UiPath> instead. That page carries its own permission, `read-senders`, so if it is not in your sidebar, ask an admin to grant it.

## No sending channel connected

The agent has nothing to send from: no email account, no LinkedIn account, no WhatsApp account. This is the first banner in the strip, and connecting any one of the three clears it. An agent set to rotate across every email account in the workspace still raises it while the workspace has none: rotating across an empty list sends nothing.

<Screenshot id="troubleshooting/agent-not-sending--alert" url="/ai-agents/9" alt="One banner on an agent's Dashboard tab reading 'No sending channel connected', with a Connect senders button on the right" caption="It clears as soon as one channel is attached. You do not need all three." marks={[{ n: 1, x: 88, y: 50 }]} />

**Connect senders** (1) opens the **Add senders** overlay on top of the page you are on: the same overlay as the **Add senders** button on the Email Accounts page. Lower down, the **Sending limits** card says the same thing in its own words, **No sending channel yet**, but its **Add a channel** button goes somewhere different: the agent's own **Settings** tab, at the **Channels** section.

## Outreach is paused while sourcing runs

Sourcing and outreach pause independently, so an agent can keep finding companies while nothing contacts them. This banner is up whenever outreach is off and at least one of the agent's lead sources is still running.

**Resume outreach** acts in place: no page change, no dialog. It shows a spinner while it works, then confirms with an **Outreach resumed** toast and reloads the agent, which takes the banner away. If the request fails, a generic error toast appears instead and the banner stays exactly where it was.

<Note>
  If this is the agent we built for you at signup, seeing this banner next to **No sending channel connected** is expected, not a sign anything is broken. That agent is created with outreach switched off, and its lead sourcing is set in motion on its own, both before you have had a chance to connect anything to send from.
</Note>

## Some senders need attention

The channel itself is connected, but at least one of the email accounts behind it has stopped working: the banner fires for any account on this agent sitting at status **Error**. When the agent rotates across the whole workspace, that means every account in it; otherwise only the ones picked for this agent. **Review senders** leaves the agent and opens **Email Accounts**.

There, the account carries an **Error** chip. Hover it and the tooltip explains why: the account's own status message when there is one to show, or a plain **Connection error** when there is not.

## Nothing left to send today

The channel is connected and accounts are attached, and the agent still sends nothing. In the row for that channel, the **Sending limits** card replaces the usual sent-today count with the reason:

* **Today's limit reached — resumes tomorrow** (1): there was an allowance today and it has been spent. Sending resumes tomorrow on its own.
* **Nothing available to send today**. The allowance itself is zero, and warm-up is not the reason: the accounts behind it are paused or in error, or the daily limit is split across enough active campaigns that this agent's slice comes to nothing.
* Warming up: the allowance is zero because the accounts are new, and sending starts once they have aged. That one also resolves on its own.

<Screenshot id="troubleshooting/agent-not-sending--limits" url="/ai-agents/9" alt="The Sending limits card for a connected email channel, reading 'Today's limit reached' with 'resumes tomorrow' beneath it, in place of the usual sent-today count" caption="A representative example. The numbers are simulated, since no seeded mailbox reaches zero on its own. The wording is the real product's." marks={[{ n: 1, x: 50, y: 68 }]} />

Underneath, campaign email is metered per account. Before each send, the count of campaign email that account has already sent today (warm-up mail does not count) is checked against its daily limit, and once the count reaches the limit that send is skipped rather than delivered. The same gate skips outbound when today is a public holiday in the lead's own country. One thing is exempt from both: a reply, meaning the last message in that thread came from the lead. Nothing else is.

The card's own tooltip is direct about why the number itself moves on its own: new mailboxes and accounts warm up gradually, limits follow inbox health, and they are split evenly across every active campaign sharing the same account.

## Resting today

Everything above checks out and one account still sends nothing today. On the Email Accounts page it carries a small **Resting today** chip; open the account itself and the same thing appears as a full notice titled **This mailbox is resting today**.

Nothing is wrong with it. Every so often a healthy account sits a whole day out on purpose, so it is not sending the same volume at the same times every single day: the pattern that reads as automated to a spam filter. The decision is made once per account per day, so it is a genuinely quiet day rather than a pause that lifts after lunch. Replies to leads still go out as normal; only new outreach and follow-ups wait until tomorrow.

## Related

<CardGroup cols={2}>
  <Card title="Agent alerts and what to do about them" icon="bell" href="/en/ai-agents/agent-alerts-and-issues">
    Every banner an agent can raise, not just the ones covered here.
  </Card>

  <Card title="Agent statuses and pause options" icon="toggle-left" href="/en/ai-agents/agent-statuses-and-pausing">
    Sourcing and outreach pause independently: the six statuses that result.
  </Card>

  <Card title="Daily limit is set to 0 during quarantine" icon="gauge" href="/en/troubleshooting/why-is-my-sending-limit-so-low">
    Why a particular mailbox's limit is low or zero in the first place.
  </Card>

  <Card title="This mailbox is resting today" icon="coffee" href="/en/troubleshooting/sender-shows-active-but-nothing-delivers">
    Every other reason an Active mailbox can still deliver nothing.
  </Card>
</CardGroup>