# Pause an agent and read its scan history

URL: https://useembers.com/help/signals/agents-pause-and-scan-history/
Category: Signals and agents
Updated: 2026-11-20
Last verified: 2026-11-20

> Pause and resume an agent from the Agents page, see what pausing stops, and read each run in its scan history, including empty and failed scans.

Agents are meant to be left running, but you may want to stop one: you are between campaigns, a watched profile went quiet, or the queue is fuller than you can work. Pausing is the switch for that, and the scan history shows what each run did.

## Pause or resume an agent

### Open Agents

Go to **Agents** (`/agents`). Each agent has a card with its status, how many leads and engagers it found, and when it last ran. The Keyword Tracker counts **authors** instead of engagers: its people wrote the posts it found.

### Flip the switch on the card

The switch at the bottom of the card pauses or resumes that agent. On **Your profile** it pauses or resumes both your posts and your comments. A toast confirms "Agent paused" or "Agent resumed".

### Or use the details

**View details** opens the agent's panel, where **Pause agent** and **Resume agent** do the same thing. On a paused agent **Resume agent** is the panel's blue button; **View leads**, beside it, opens the leads the agent found.

Anyone on the workspace can pause or resume. The banner at the top of the page sums up the whole fleet, for example "2 of 5 agents paused". What each banner line means is in [find out why your agents stopped scanning](/help/troubleshooting/agents-not-scanning/).

## What pausing stops

While an agent is paused:

- **Scheduled scans are skipped.** The card reads **Paused**, and **Next scheduled run** in the details reads Paused instead of a date.
- **Retries are refused.** A retry returns "Agent is paused. Resume it before triggering a scan."
- **Rescoring goes quiet when everything is paused.** Score updates, ICP re-checks, and profile refreshes only run for a workspace with at least one unpaused agent. Pause every agent and the notifications that scoring produces stop too.

> **Warning: Resuming needs a paid plan**
>
> When the workspace drops to Free, Embers pauses every agent for you, and resuming is refused with "This agent cannot be resumed until the workspace is on a paid plan." When a plan starts, the agents Embers paused resume on their own. An agent you paused yourself stays paused until you resume it. See [what happens when the trial ends](/help/account-and-billing/free-trial/#when-the-trial-ends).

Pausing keeps a watched profile's slot. To free the slot, remove the profile instead: **Remove from watchlist** in a Watchlist Tracker's details, or from the [Watchlist](/help/signals/watchlist/). Either way, "Removed from watchlist" offers **Undo** for a few seconds, which puts the profile back with its history and leads. Paused profiles still count toward your [watched profile cap](/help/account-and-billing/linkedin-accounts-and-seats/).

## Cadence

Every agent scans every 24 hours, and that is the only cadence. The card reads "Every 24 hours · last ran 3h ago". In the details, **Running cadence** repeats it and **Next scheduled run** shows the date, or **Soon** when a run is due. There is no button to scan on demand.

## Read the scan history

**View details** opens with the agent's name, its status, and what it does on one line; choose **More** to read the rest, and **Less** to fold it. Then come the agent's totals (**Leads found**, **Engagers found** or, for the Keyword Tracker, **Authors found**, **Scans completed**, and **Posts scanned** or **Comments scanned**), then the **Scan history**, most recent first. **Your profile** shows **Posts scanned** and **Comments scanned** in place of **Scans completed**, counts each person once, and lists its post and comment scans together.

A finished run is a plain row with no label: its date and time, then the posts or comments it read, the engagements it found, and how long it took, as in "Oct 5, 1:54 PM · 5 posts · 109 engagements · 35s". The Keyword Tracker's rows show authors, relevant posts and leads in place of engagements, or **Still checking** while it scores them. Only a run that is not the usual has a word before its time:

| Word | Meaning |
| --- | --- |
| Queued | The run was created and is waiting to start |
| Scanning… | Embers is reading public LinkedIn data |
| Processing… | The data is being matched, classified, and scored |
| Failed | The run stopped, in red; the reason is under it |

So a failed run stands out from the finished ones around it.

While a run is in progress, a banner reads "Scan queued", "Scanning LinkedIn", or "Processing data". After the second completed scan, a **Scan activity** chart plots the last ten runs.

## What an empty scan means

A completed run that reports zero posts or zero engagements is not a fault. After the first run, each scan collects only what is new since the last one, so a day with no new public posts and no new engagement produces an empty but successful run. See [what the first scan reads](/help/signals/history-lookback/#every-scan-after-the-first).

If every run has been empty from the start, the cause is upstream of the agent: no public posts, no engagement on them, or nobody clearing your ICP. Work through [no leads in your queue yet](/help/troubleshooting/no-leads-yet/) rather than pausing and re-adding the agent.

## Troubleshooting

When the latest run failed, the details show **Scan did not complete** with the reason and a **Retry scan** button:

- **"LinkedIn could not read this profile. Check that the URL is correct and the profile is public."** Fix the URL or make the profile public. For a watched profile, remove it and add it again with the right URL.
- **"LinkedIn data was temporarily unavailable. Retry the scan or wait for the next scheduled run."** Choose **Retry scan**, or leave it. A failed Watchlist or keyword scan is retried on its own after 15 minutes. After three failed scans in a row, it waits for its next scheduled scan instead.
- **A watched profile's scan finished without their comments.** When the comments that person left on other posts, or the reactions to those comments, cannot be read, the scan still finishes with their posts and the engagement on them. The next scan tries the comments again.
- **A run shows Scanning or Processing for hours.** A run stuck for more than two hours is closed automatically, so it cannot block the next one.
- **The card reads Inactive, or the banner says On hold.** The plan or the trial cap stopped the agents, not a fault. See [find out why your agents stopped scanning](/help/troubleshooting/agents-not-scanning/).

A single failure between good runs is almost always a temporary gap in LinkedIn data. Look for several failures in a row before changing anything.

## Related

- [Find out why your agents stopped scanning](/help/troubleshooting/agents-not-scanning/): Read the fleet status and restart agents.

- [What the first scan reads](/help/signals/history-lookback/): Why the first run looks so different.

- [Watch any public LinkedIn profile](/help/signals/watchlist/): Remove a profile instead of pausing it.

## Frequently asked questions

**Does pausing an agent delete anything?**

No. Pausing stops scheduled scans. Every lead, score, note, and past run stays where it is, and resuming picks up from there.

**Why can I not resume my agent?**

The workspace is not on a paid plan, or a trial has used its engagements and the plan has not started yet. The message you see says which.

**Can I make an agent scan more often, or right now?**

No. Every agent scans every 24 hours, and there is no scan now button. A failed scan can be retried from the agent's details.
