Start, stop, and monitor a run
Request a manual run, follow its live state, and understand what stopping preserves.
When to use this
Use a manual run to test a profile now or add prospects outside a worker schedule.
Requirements and availability
- A ready Agent, complete profile, and enough credits for run size and research budget.
- Manual runs can be unavailable while an eligible Free starter batch is active. Its scheduled batches continue after the first run stores the required prospects; follow them on Agent and Runs.
How to do it
- Open Agent.
- Choose the profile or worker and review Effort and target.
- If the starter batch is active, wait for its scheduled run. Otherwise select Run agent or Run now once when available.
- Wait for Run started, Queued, or Running rather than submitting again.
- Open Runs and open the run timeline.
- If necessary, select Stop this run and confirm.
Fields and controls
| Control | What it does |
|---|---|
| Run started | The request was acknowledged; continuing progress appears in status cards. |
| Starting… | The request is still being submitted. |
| Stop this run | Requests cancellation for queued or running work. |
| View log | Opens the customer-visible event timeline. |
What happens next
Active runs update automatically. Stopping preserves records delivered before cancellation.
States you may see
| State | Meaning |
|---|---|
| Queued | Accepted but not picked up yet. |
| Running | Actively researching and qualifying. |
| Delivered | A run outcome meaning its delivery count reached the requested target. Check the individual destination record for external delivery. |
| Partial / No prospects | Completed below target. |
| Cancelled | The run ended before completion. This may follow a Stop request or a system cancellation such as a no-progress deadline; check events before assuming who stopped it. |
| Stopped (low yield) | Ended because continued sourcing produced too few qualified matches. |
Credits and usage
Stopping retains used credits and delivered records. Unused reserved credits are released when the run ends.
Common problems
| Problem | What to check |
|---|---|
| The button remains active | Check Runs before clicking again; the request may already exist. |
| The run finishes below target | Inspect events, then review requirements and profile scope. |