Runs
How runs execute jobs and produce extracted data.
A run is a single execution of a job. Each run visits the target site, extracts the data, and produces a set of items you can download or query.
How Runs Work
When you create a job, the first run is created automatically alongside it. Once the job's processing step completes and the job becomes ready, the run begins scraping.
After the first run, you can trigger additional runs — called reruns — at any time. Reruns skip the processing step entirely and go straight to scraping, which makes them faster and cheaper (no processing fee).
Run States
| State | Meaning |
|---|---|
| Queued | The run is waiting to start |
| Scraping | The run is actively visiting pages and extracting data |
| Completed | All pages have been scraped — data is ready |
| Failed | Something went wrong — check the error message |
Progressive Results
You don't have to wait for a run to finish. Extracted items appear progressively as each page is scraped, so you can start reviewing data while the run is still in progress.
Reruns
Reruns are useful whenever you need fresh data from the same site — for example, to track price changes, monitor new listings, or refresh inventory counts. Each rerun produces a new, independent set of items.
If you need reruns on a regular cadence, consider setting up a schedule to automate them.