> ## 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.

# Your first agent: what to do when something looks wrong

> The banners a new agent can show, the onboarding failures you can hit, and what to do about each.

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>;
};

An agent puts every problem it knows about in a banner across the top of its **Dashboard** tab, and a workspace created at signup arrives with three of them already showing.

<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, and what the numbers mean

Open the agent from <UiPath>Outreach → AI Agents</UiPath> and stay on its **Dashboard** tab. The banners sit at the top of it, above the activity feed and the side rail. Each one carries a title, a line explaining it, and the button that deals with it.

One card can sit above them, and only one. That is the [first-leads card](/en/getting-started/first-leads-what-to-expect), and it appears for a while on an agent you launched yourself from the creation wizard. The agent built for you at signup never shows it, so on that agent the banners really are the first thing on the tab.

When an agent has nothing wrong with it there are no banners at all. The strip is absent rather than empty, so a bare dashboard is a good sign.

Two other tabs repeat a subset. The **Settings** tab raises the missing sending channel and the goal with no call-to-action, because those two are the ones you fix there. The **Sources** tab raises the two sourcing problems. Everything else appears only on the **Dashboard** tab.

<Note>
  On the agents list, each agent carries a count of its open issues next to its status. That count is worked out from what the list already loaded, and two problems, **No leads matched yet** and **No WhatsApp-reachable leads yet**, are judged from figures only the agent's own page fetches. The list can therefore show a smaller number than the agent does. The **Dashboard** tab is the one to trust.
</Note>

The banners come in a fixed order, not in order of urgency: the sending channel first, the sourcing ones last.

## The three banners every new agent shows

None of the three is a fault. They are the three things the product deliberately leaves for you, and it raises them in this order: something to send from, the go-ahead to start sending, and somewhere to send people.

<Screenshot id="getting-started/troubleshooting-your-first-agent--post-onboarding-stack" frame="bare" alt="Two stacked banners at the top of an agent dashboard: 'No sending channel connected' with a Connect senders button, and 'Outreach is paused while sourcing runs' with a Resume outreach button" caption="The first two, as they arrive. The goal banner sits under them in the same strip." marks={[{ n: 1, x: 88, y: 24 }, { n: 2, x: 88, y: 74 }]} />

### No sending channel connected

The agent has nothing to send from: no email account, no LinkedIn account and no WhatsApp account. A new workspace has none, which is why this is the first thing a first agent says.

**Connect senders** (1) opens the Add senders overlay on top of the page you are on, rather than sending you to the **Email Accounts** page. [Connecting your first mailbox](/en/getting-started/connect-your-first-email-account) is a page of its own.

An agent set to rotate across every email account in the workspace still shows this banner while the workspace has no email account. Rotating across an empty list sends nothing, so the banner is correct.

### Outreach is paused while sourcing runs

The agent's lead sourcing is producing and its outreach is switched off, so leads are arriving and nobody is contacting them.

It appears only in that exact combination. A source that is queued and has not started yet does not count as running, so a workspace whose first search is still waiting its turn sees no banner here even though outreach is off.

**Resume outreach** (2) acts where you are: no page change, no dialog. The button shows a spinner while it works, then confirms with **Outreach resumed**. If it fails, a general error message appears and the banner stays.

### Goal is missing its call-to-action

The agent knows what it is trying to achieve but has nowhere to send anyone. Your first agent is built with its goal set to **Meeting Link** and no link attached to it, so this banner is up from the moment the agent exists.

**Set up goal** opens the **Goal** section of the agent's **Settings** tab. There you can give the meeting goal a destination: pick one of your meeting links, or paste a booking URL from any other calendar tool. You can also change the goal to **Website Link**, **WhatsApp** or **Custom**.

Every goal has its own field, and the banner clears when that field is filled. That is a link for a meeting, a website address, a phone number, or the description you write yourself for a custom goal.

<Warning>
  Clearing one of the three does nothing for the other two. Resuming outreach leaves the missing-channel banner exactly where it was, connecting a mailbox does not resume outreach, and neither of them touches the goal. A new workspace has all three to deal with.
</Warning>

## When sourcing stops

### Sourcing paused: out of credits

At least one of the agent's lead sources stopped because the workspace ran out of credits. If you are still on a trial, [what your trial credits cover](/en/billing/free-trial-credits) is worth reading before you buy more.

**Get more credits** opens the subscription dialog over the page. It does not navigate anywhere, so you keep your place on the dashboard.

Once the workspace has credits again, you do not have to restart anything. That applies whether you bought credits or a new billing period started. We re-check every source paused for this reason on a schedule, and put the ones that can pay back to work. It is not immediate. The source stays paused and the banner stays up until that check next runs, so a source still sitting there a while after a top-up is behaving normally.

<Screenshot id="getting-started/troubleshooting-your-first-agent--no-credits" frame="bare" alt="A banner reading 'Sourcing paused,' warning the workspace is out of credits, above the line 'Your agent stopped finding new companies because the workspace ran out of credits', with a Get more credits button" caption="The button opens the subscription dialog in place. You do not leave the agent." />

### Sourcing reached its company limit

At least one source has analyzed every company its limit allows.

The same banner, with the same words and the same button, also appears when every one of the agent's searches has finished: a different situation with a different meaning. Two things tell them apart:

* The **Setup checklist** in the side rail counts sourcing as done for a finished search, and leaves it needing attention for a source stopped at its limit. A green checklist row under an amber banner means the searches finished.
* The **Sources** tab raises this banner only for the limit case. If the banner is on the **Dashboard** tab and not on the **Sources** tab, the searches finished.

**Increase limit** edits one number, that source's company limit. It opens a small editor next to the button, so you never leave the dashboard. When more than one of the agent's sources is exhausted the button cannot know which you meant, and it switches to the **Sources** tab instead.

<Screenshot id="getting-started/troubleshooting-your-first-agent--company-limit" url="/ai-agents/12" alt="An agent dashboard showing the 'Sourcing reached its company limit' banner with the inline company-limit editor open beside its Increase limit button" caption="One exhausted source is edited in place. Two or more, and the button gives up and opens the Sources tab." />

## The other banners a first agent can raise

| Banner                                     | What it is telling you                                                                     | Its button                                                                    |
| ------------------------------------------ | ------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------- |
| **Some senders need attention**            | One or more of the email accounts this agent can use stopped sending                       | **Review senders** opens the **Email Accounts** page                          |
| **No tag linked to this agent**            | The agent has no tag, so it cannot claim leads, a funnel or metrics of its own             | **Link a tag** opens the agent's **Settings** tab                             |
| **No leads matched yet**                   | Sourcing analyzed companies and none of them cleared your criteria                         | **Adjust targeting** opens the **Sources** tab                                |
| **No WhatsApp-reachable leads yet**        | The agent sends only on WhatsApp and none of its leads has a phone number                  | **Review channels** opens the channel section of the agent's **Settings** tab |
| **WhatsApp accounts can't send right now** | Every WhatsApp account on the agent is out of budget for today; sending resumes on its own | **Review accounts** opens the WhatsApp accounts page                          |

The missing channel and the goal with no call-to-action are the two the product treats as blocking, and the two that also put a dot on the **Settings** tab. Nothing in this table is marked that way. [Agent alerts and what to do about them](/en/ai-agents/agent-alerts-and-issues) covers all of them in full.

## When onboarding itself goes wrong

<Note>
  The onboarding wizard is shown in English whatever language the rest of the app is set to.
</Note>

### "We couldn't analyze that website. Let's set it up manually."

The analysis of the website you entered failed. The wizard moves you straight to the first of its four manual questions: what your business is called, what it does, its language, and the industries you sell to. Those are the same four fields the analysis would have filled in, so nothing is lost but the typing. The address you entered is kept.

Going back from that first question returns you to the website field, so you can correct the address and try again rather than typing everything out.

<Screenshot id="getting-started/troubleshooting-your-first-agent--scrape-failed" alt="The onboarding wizard showing a warning toast reading 'We couldn't analyze that website. Let's set it up manually.' above the first manual question, which asks what the business is called" caption="A representative example, reproduced rather than seeded. The wizard never dead-ends: it always has a manual path." />

### The analysis is taking too long

The wait screen narrates what it is doing one line at a time. That narration is the same timed script the product runs everywhere it waits on a model. It is not reporting progress, and it never announces that it finished.

If the analysis runs long, a panel appears under it headed **This is taking longer than expected**, offering **Keep waiting**, **Continue manually**, and (only if you already belong to a workspace) **Back to workspaces**. A **Change website** link sits under the caption the whole time, panel or no panel.

**Keep waiting** only dismisses the panel. The analysis was never stopped and it moves you on by itself if it finishes. The other three stop the app waiting for it.

### We couldn't build your first agent

Your first agent is built for you after onboarding, on our side. While that runs, the AI Agents page shows a card headed **Generating your first AI agent** with a list of stages beside it. Those stages are a timed animation: one lighting up does not mean it finished.

If the build fails, the card replaces the stages with **We couldn't build your first agent** and a single **Try again** button, which starts the build again and goes back to waiting. If the full-screen tour that opens over the page is still up, the same message and the same button appear there instead.

While the card is waiting, it checks the build's status on a loop. A check that fails on its own (a dropped connection, a moment of network trouble) is swallowed and tried again. A card still showing stages is therefore not hiding an error from you.

**Try again** does not work that way. If the request that restarts the build cannot be sent at all, the same failure message comes straight back. Press the button again.

<Screenshot id="getting-started/troubleshooting-your-first-agent--generation-failed" frame="bare" alt="The first-agent card in its failed state: the heading 'We couldn't build your first agent', the line 'Something went wrong while setting things up. You can try again, or create an agent manually.' and a Try again button" caption="A representative example, reproduced rather than seeded. This is the only first-agent failure that offers you a retry." />

### The AI Agents page is empty and nothing is being built

You land on the AI Agents page after onboarding and find no agents, no card and no error. That means the request that starts the build never landed. Onboarding does not stop for that, it takes you into the workspace anyway, so the failure looks like an empty page.

There is nothing to retry from that screen. Build one yourself with **Create AI Agent**, or use **Suggest with AI** to have the setup proposed for you, following [your first AI agent](/en/getting-started/your-first-ai-agent).

The card is also remembered only for the browser tab you finished onboarding in. Open the workspace in another tab, or come back after closing the browser, and the card is gone even though the build may still be running. The list refreshes itself while you watch it, so the agent appears on its own once it is ready.

## Related

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

  <Card title="The agent setup checklist explained" icon="list" href="/en/getting-started/setup-checklist">
    The card in the side rail, and why it can disagree with a banner.
  </Card>

  <Card title="No sending channel connected" icon="send" href="/en/troubleshooting/agent-not-sending">
    Every reason an agent sends nothing, in the order worth checking.
  </Card>

  <Card title="No leads found" icon="search" href="/en/troubleshooting/no-leads-found">
    What to change when sourcing runs and nothing matches.
  </Card>
</CardGroup>