# A model regression, the skip limit, and a restart with a fixed model

Execution 1: simulated model returns invalid JSON for 50% of tickets, no re-ask, skip limit 50, 2,000 tickets.
  status / reason         FAILED / org.springframework.batch.core.step.FatalStepExecutionException: Unable to process chunk
  tickets read            200 of 2000
  calls the provider billed before the step stopped: 200  (a full run needs about 2,000)
  committed results       52     skipped rows 50

Execution 2: same job parameters, same database, model fixed, skip limit 1000.
  status                  COMPLETED
  tickets read this time  1900    (execution 1 had committed 100, so the reader resumed after them)
  committed results       1942     skipped rows 58     classified + skipped = 2000
  tickets present in BOTH tables: 0  (stale skip rows from execution 1 are deleted when the ticket is classified)