cURL
How Cancellation Works
Cancellation is a signal, not instant:- Active work units finish gracefully, no new work is scheduled
- Matches found so far are preserved and accessible
- You’re charged for work completed during cancellation
- After cancellation, the run transitions to
cancelledstatus (see Run Lifecycle)
Cancelled runs cannot be extended or enriched. Cancellation is irreversible—you’ll need to create a new run to continue searching.
Common Use Cases
- Control costs when a run takes longer than expected
- Stop after finding enough matches (monitor via webhooks or SSE)
- Iterate quickly with refined queries instead of waiting for completion
Related Topics
- Generators and Pricing: Detailed pricing information and examples
- Preview: Test queries with ~10 candidates before running full searches
- Enrichments: Extract additional structured data for matched candidates
- Extend Runs: Increase match limits without paying new fixed costs
- Streaming Events: Receive real-time updates via Server-Sent Events
- Webhooks: Configure HTTP callbacks for run completion and matches
- API Reference: Complete endpoint documentation