Continuing job after crash

[wardstoneX]

Is there a way to continue a job after it crashed halfway ? I don't want it to start froms 0, but to start from where it left off. Also what exacatly is jobs/min, is it places we scrape per minute?

{"level":"info","component":"scrapemate","numOfJobsCompleted":131,"numOfJobsFailed":0,"lastActivityAt":"2026-06-12T09:22:53.674403881Z","speed":"26.20 jobs/min","time":"2026-06-12T09:22:56.332042829Z","message":"scrapemate stats"}

also anyone knows why we get this error?
{"level":"error","component":"scrapemate","error":"playwright: TypeError: Cannot read properties of null (reading 'scrollHeight')\n at eval (eval at evaluate (:290:30), :3:21)\n at UtilityScript.evaluate (:297:18)\n at UtilityScript. (:1:44)","time":"2026-06-12T10:10:37.364499675Z","message":"error while processing job"}

ps: i use the CLI

[iSerter]

This is happening for me too. I use the API endpoint.

"level":"info","component":"scrapemate","job":"Job{ID: 4c9f4580-fd4e-42d8-a631-3549415ce30e, Method: GET, URL: https://www.google.com/maps/search/web+design+agency, UrlParams: map[hl:en]}","error":"playwright: TypeError: Cannot read properties of null (reading 'scrollHeight')\n    at eval (eval at evaluate (:313:29), <anonymous>:3:21)\n    at UtilityScript.evaluate (<anonymous>:320:18)\n    at UtilityScript.<anonymous> (<anonymous>:1:44)","status":"failed","duration":29454.154227,"time":"2026-07-07T15:35:32.262454228Z","message":"job finished"}
{"level":"error","component":"scrapemate","error":"playwright: TypeError: Cannot read properties of null (reading 'scrollHeight')\n    at eval (eval at evaluate (:313:29), <anonymous>:3:21)\n    at UtilityScript.evaluate (<anonymous>:320:18)\n    at UtilityScript.<anonymous> (<anonymous>:1:44)","time":"2026-07-07T15:35:32.262462991Z","message":"error while processing job"}

[wardstoneX]

i am not fully sure but there might not be enough threads available or cpu cores available, i have a limit of 1500 threads and c=12 already almost fully uses it, but idk

[gosom]

Hello,

jobs/min is places per minute.

I am trying to see how resume can be added. The problem at the moment is that we don't know how many places each query has. Probably we need to change the way a query is processed in something like:

• process all pages and save the places
• process all the places for the query

and when each query finishes all it's places we should persist that and add a resume functionality.

I will try to work on this

[gosom]

#313