Monitor running agents in the task feed

When you run an agent, qualify or research records, find contacts, or run a workflow, the work happens in the background. The task feed is where you watch it. Every task shows what it is doing, who started it, how far along it is, and whether it finished, errored, or was skipped. Use it to confirm a run actually started, to track progress on a large batch, and to stop something that is still queued or running.

There are two places to look: a global feed that covers the whole workspace, and a per-record view that shows only the tasks touching one account or contact.

Where the task feed lives

Global feed. In the top header, click Task feed. A panel opens with your five most recent tasks. Click View all to open the full Agent tasks feed page, where you can filter, page through history, and stop running tasks.

Per-record feed. Open an account or contact, go to its Activity tab and stay on Agent tasks. This lists only the tasks for that one record. While work is in progress on the record, an indicator appears on the Activity tab label so you can spot active runs without opening it. Click a task card here to expand it in place and see that record’s own journey through the run’s steps, without opening a separate view.

Both views refresh on their own every five seconds, so progress and new tasks appear without reloading the page.

By default, the header panel and the full Agent tasks feed page show only the tasks you started yourself, so your view stays focused on your own work rather than the whole team’s. Change the Created by filter on the full feed page to see a teammate’s tasks too.

Reading a task

Each task is a card. From left to right it shows:

An icon for the kind of work (a distinct icon marks tasks that came from a workflow).
A plain-language description of what the agent is doing, who it is for (the account or contact), and on finished tasks a running count of results, for example how many accounts came back ICP yes, how many contacts were found, or how many plays were generated.
The time it was created and the name of the person who started it, shown after by.
The current status and a progress bar.

Statuses

The status reads as one of:

In queue - the task is accepted and waiting to start.
In progress… - the task is running now. The card shows an animated border while it runs.
Finished - the task completed.
Stopped - the task was cancelled before it finished.
Out of credits - the task stopped partway through because your company ran out of credits. Records already completed keep their results. See Resume a run that stopped for credits below.
Error - the task could not be completed.
Skipped - the task did not run for that record, for example because there was nothing to do.

When a task carries extra context about a problem, an information tip appears next to the status. If your ecosystem structure has a logic issue, the tip points you to contact your customer success manager.

The progress bar breaks the batch into Completed, In progress, and In queue so you can see how much of a large run is done.

Filtering the feed

On the full Agent tasks feed page (and the per-record Agent tasks view) you can narrow the list with these filters:

Status - pick one status (In queue, In progress, Finished, Stopped, Out of credits, Error, or Skipped). Status is single-select; the others let you pick more than one value.
Action - the kind of work, such as qualifying accounts or contacts, researching, finding contacts, generating plays, or finding domains.
Source - where the task was started from, such as the Data Hub or a workflow.
Created by - the person who started it. Set to you by default; clear it or pick other names to include teammates’ tasks.
Date added - a from/to date range.

Tasks are listed newest first.

Opening the record a task ran on

Click any task card to jump to the matching records. Account-side tasks (qualification, research, account plans, domain finding) open in Accounts filtered to that run; contact-side tasks (contact finder, research, plays, the digital twin, email and phone finding) open in Contacts filtered to that run.

On the full feed page you can also select several tasks at once and use Open in Accounts or Open in Contacts to view all of their records together.

Seeing the run report

Open the menu on a task card (the three-dot button) and choose one of two views: Run overview for the shape of the whole run, or Per-record breakdown to look at what happened to one specific account or contact.

Run overview

Whether the run was a single agent or a multi-step workflow, Run overview is a visual map of the steps it used: each step is a card, laid out top to bottom and connected in the order the run executed, so you can see the whole motion at a glance and read how records moved through it.

The flow, drawn out. Every step appears as a card showing the agent’s name and, as records complete, a row of small status counts (hover one to see what it counts - completed, skipped, and so on) together with how long the step took. A branching step fans out into its paths, each labelled with how many records went down it, and a path that ends is marked End of flow. If the run loops a step, each pass shows as its own card, so the repetition is visible rather than hidden. A step no record has reached yet is left off the map entirely, and when two paths lead back to the same next step, that shared continuation is drawn once beneath them instead of being duplicated under each path - so the map reflects what the run has actually done, not every step in the configured setup.
Click a step for detail. Selecting a card opens a panel with three parts. Statistics breaks the step down into how many records completed, are in progress, are pending, were skipped, or hit an error, plus the step’s total time and its average, fastest, and slowest per record. When a step has skipped or errored records, an expandable Why were N records skipped? or Why did N records fail? disclosure lists the specific reasons - for example no research agent assigned to a persona type, or an invalid domain - each with how many records it applied to, so you can see the cause without opening individual records. Results shows the outcomes the agent produced, grouped by kind - for example how many accounts came back ICP yes or no, a breakdown of why contacts were disqualified (out of date at their company, seniority or expertise mismatch, and so on), how many contacts were found per persona, and how many verified emails and phone numbers were returned along with which data vendor supplied each. Switch between All, New this run, and Reused to tell fresh work from outcomes carried over from an earlier run - All is the combined total and is shown by default. Setup is a read-only summary of how the step was configured for this run, such as which verticals it checked against or which plays it wrote.
Move around the report. Drag an empty part of the canvas to pan, and use the zoom controls in the bottom-right corner (a minus and a plus, with the current percentage between them; click the percentage to reset it). While a run is still going the report refreshes on its own every few seconds, so the counts fill in live.
Opens on the step you’re waiting on. On a run that’s still going, the report centers itself on the first step that is in progress (or, if nothing is running yet, the first one still queued) rather than the start of the flow - useful on a long run where the early steps already finished and you want to see what’s happening now. This only happens once when you open the report; if you pan elsewhere yourself, later refreshes will not pull the view back.

Per-record breakdown

Choose Per-record breakdown to search the run’s records by name, pick one, and see just its own journey: the steps it went through, in the order it went through them, each shown as a small icon for the agent that ran it, plus a dashed icon for any branching decision along the way and which way it went. Expand a step in that journey to see what it logged for this specific record - contact-finder results, qualification checks, which criteria were researched, and similar per-agent detail. When the run only ever covered one record, this view skips straight to that record’s journey instead of asking you to search for it. Use this when you already know which account or contact you care about and want its story directly, rather than reading it out of the whole run’s aggregate statistics.

Resume a run that stopped for credits

If a run stops with the Out of credits status, a Continue workflow button appears - on the task card itself, and inside both Run overview and Per-record breakdown - so you don’t have to start the batch over. Clicking it picks the run back up from where it paused; records already completed are not redone.

The button is available to anyone with permission to launch workflows. It stays disabled, with a tooltip explaining why, until your workspace has credits again - use the Top-up link shown next to the message to reach the top-up page, or see Top up your credits. Once the workspace has credits, click Continue workflow to resume.

Stop a running task

You can stop a task that is In queue or In progress. Stopping is available from the full Agent tasks feed page, not from the per-record Agent tasks view. You can stop tasks you started yourself; full-access members can stop any task.

On the Agent tasks feed page, find the task you want to stop.
Open its menu (the three-dot button on the right of the card) and choose Stop.
A Stop task? confirmation appears, naming the task. Click Stop to confirm.

You will see a Task stopped successfully message, and the task moves to the Stopped status. Any records already finished before you stopped keep their results; the remaining queued records are not processed.

What happens next

New tasks appear in the feed within a few seconds of starting a run. A task moves through In queue to In progress to Finished as the agent works through the batch; the progress bar fills as records complete. The time a run takes depends on the kind of work and how many records are in it.

When a task reaches Finished, its results are written to the relevant records. Click the card to open those records, or open Run overview for the step-by-step breakdown, or Per-record breakdown to check one specific record. If a task lands on Error, see Fix an agent job error. If a record shows as Skipped, see A record was skipped. If a task stops as Out of credits, see Resume a run that stopped for credits above.