EloshonHow-to guide
Resume a stopped job
A scraping stopped before the end: you closed the app, clicked Stop…, or the site blocked it. From Jobs, you resume it where it stopped.
Checked against the software on November 1, 2026
The case: last night, you started reading the home page of Atelier Démo, atelier-demo.example.com, then closed the app before the end. This morning, the job shows Interrupted.
Before you read a site
Check the site's terms of use and the rights to its content (text, photos, trademarks) before you read or reuse it. Each user remains responsible for how they use the data they read. This note is general information, not legal advice.
Resume the job
- In the left bar, click Jobs.
- On the job's row, click Resume.
- Read the Resume the interrupted job? window: it shows what is already processed and what is left.
- Click Resume the job.
The scraping starts again on the progress screen. Only the addresses not processed yet are read, and the products already read stay in the job. If the search for products had found nothing before the stop, it starts again from the start page.
When Resume is offered
- On a job stopped before the end: interrupted, blocked by the site, stopped for lack of progress or by the quality check. The end screen says so too, for example 85 URLs remaining: The job can be resumed from the Jobs tab, right where it stopped.
- Not on a job that ran to the end, even one marked Partial because a limit such as Max products was reached, nor on a failed job (Failed): it offers Results. Without any product, it offers Run again with the browser… instead.
- Not on a job read in your browser, marked Your browser: it cannot be resumed.
What a resume keeps, and what it changes
- It keeps the address, the source, the product type, the browser identity and the Browser when the page needs it choice of the first start.
- It uses the limits and network settings saved in Settings, not the ones typed in New scraping at the first start.
- It runs without Manual intervention: if the site asks for a check again, the job stops again as on a blocked site.
To pass a check yourself
Start a new scraping from New scraping instead, with Manual intervention on. That new job starts again from the start page; the old one stays in Jobs with its products.
Start again with the browser
Run again with the browser… appears on a job that finished, or failed, without any product. It does not resume the old job: it copies its address into New scraping, with Browser when the page needs it and Manual intervention on. Then click Start scraping: a new job starts.
Check
In Jobs, the job's row, the same one and not a new one, changes to Running, then to its final status. The Products column goes up; when the job runs to the end, Results shows all the products, old and new. If the status stays Blocked, rest the mouse on the status to read the reason, then read Why a site refuses to be read.