Skip to content
Batches

Runs: each time a batch works

A run is one execution of a lobstr.io batch: how it starts, its statuses, how to stop, resume or continue it, what its page shows, and how long its results are kept.

A run is one execution of a batch: the batch is the setup, the run is the work, with its own results, credits and logs. Each launch, by hand or on a schedule, makes a new run.

How a run starts

  • By hand: click Launch on the batch's page.
  • On a schedule: a batch set to Repeat launches by itself. See Scheduling.
  • From code or your agent: through the API v1 with your API key, or the batches' MCP server.

A run takes the batch's settings at launch. Changing them while it runs changes the next run, not this one.

The runs list

The batch's page lists its runs, newest first:

Column What it shows
Started When the run started
Duration How long it ran
Results Every result collected
Unique Results left once duplicates are skipped, usually the number you care about
Emails Emails found, on scrapers that look for them
Credits What the run spent
Status Where the run is, or why it ended

A run that ended on a problem says why as its status, such as Out of credits; hover a status for the details. Click a run to open its page.

Statuses

Status What it means
Starting The run was launched and is getting ready
Running It is collecting results; Uploading and Verifying follow, while it exports its results and checks its emails
Paused It waits for something, then picks up where it stopped: credits, an account's limit, cookies to refresh
Stopped You stopped it. Its results so far are kept
Error It ended on a problem; the status says which
Done It finished; its results are ready to download

Every reason a run can end or pause, and what to do about it: Why a run stopped.

Stop, resume, continue

  • Stop run stops a run now. The results collected so far stay in Results.
  • Resume restarts a paused run now, without waiting for the time it would pick up by itself.
  • Continue run takes a stopped run up again, if it is the batch's latest run: done tasks stay done, unfinished ones start over. See Continue a stopped run.

What happens when credits run out depends on the batch's If credits run out setting: Pause, then resume when credits are back, or End the run. See Credits.

The run's page

Four tabs:

  • Results: a preview of what it collected.
  • Tasks: the tasks it processed, with their results, to see which input brought what.
  • Credits: where its credits went, function by function: the results, each enrichment, each extra.
  • Logs: every page, pause and error, live while it runs.

Its More menu copies its download link or its ID, shows its pause history, and opens a chat with support about this run.

Slots

A run takes the batch's Slots (its scrapers working in parallel, up to the scraper's own cap) while it is in progress. With 10 slots on your plan, you can run one batch at 10 or ten batches at 1. See Calls and runs at a time.

Launch again

Launch makes a new run, from the first task, with the batch's current settings. Results that come back again are billed again unless you skip duplicates: see Re-running a batch.

How long results are kept

A run's results can be downloaded for 7 days on Free, 45 days on Starter and Pro and 90 days on Team, from the end of the run. Each run shows when it expires, and the API v1 returns it as expires_at. After that, its results can no longer be downloaded. To keep them longer, download them or send them to Google Sheets or S3.