Pause an agent and read its scan history

Agents are meant to be left running, but there are good reasons to stop one: you are between campaigns, a watched profile went quiet, or the queue is fuller than you can work through. Pausing is the switch for that.

Pause and resume

Open the agents screen, select the agent, and use Pause Agent. The same control becomes Resume Agent while it is paused. The agent card also carries a pause control so you do not have to open the detail panel.

While an agent is paused:

• Scheduled scans are skipped. The status reads Paused and the next scheduled run shows as paused rather than a date.
• A manual scan is refused until you resume. Embers tells you the agent is paused rather than silently doing nothing.
• Rescoring goes quiet too. Score recalculation and ICP reclassification only run for accounts with at least one unpaused agent, so pausing everything also stops the notification events that scoring produces. Pause means quiet, not just “stop fetching”.

Pausing is the right tool for a temporary stop. For a watched profile you no longer care about, remove it instead: that frees the watchlist slot, while pausing does not.

Cadence

Every agent runs on a 24 hour cadence, and every 24 hours is the only cadence available. The detail panel shows the running cadence and the next scheduled run, which reads Soon when a run is due or overdue.

Reading the scan history

The detail panel lists the recent runs, most recent first, as a timeline. Each entry shows a state and a timestamp:

A completed run also shows how many posts it scanned, how many engagements it created, and how long it took. Above the timeline, the panel keeps a running count of scans completed and total items scanned, and draws a scan activity chart once there are at least two completed runs.

What an empty scan means

A completed run reporting zero posts or zero engagements is not a fault. After the first run, each scan only asks for activity newer than the last one, so a day with no new public posts and no new engagement produces an empty but successful run. That is the normal shape of a healthy account between posts.

If every run is empty from the very beginning, the problem is upstream of the agent: no public posts in the window, no engagement on them, or nobody clearing your ICP. Work through the empty queue checklist rather than pausing and re-adding the agent.

What a failed scan means

A failed run means the collection stage stopped. Embers shows a plain explanation on the run and a banner with a Retry scan button on the agent when the latest run failed. The two messages you will see are:

• LinkedIn could not read this profile. Check the URL is correct and the profile is public. This is the one that needs you to act.
• LinkedIn data was temporarily unavailable. Retry the scan, or leave it for the next scheduled run.

Runs are also self healing in two ways. A run stuck in progress for more than two hours is marked failed automatically so it cannot block the next one, and a failed watchlist scan is retried after a short cooldown rather than waiting a full cycle.

Related