Pause an agent and read its scan history

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

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

2. 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”.

3. Or use the details

   View details opens the agent’s panel, where Pause agent and Resume agent do the same thing.

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.

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.

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. Paused profiles still count toward your watched profile cap.

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 shows the agent’s totals (Leads found, Engagers 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:

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.

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

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