Batch Reprocessing
When a batch finishes with errors, you don’t need to re-run the entire batch. Dobermann lets you reprocess only the transactions that failed — keeping completed results intact and saving time.
Reprocess is for a batch that has finished. A paused or cancelled batch has rows still to send: Resume it instead.
Quick Start
- Run a batch from the Console
- Once the batch finishes (or finishes with errors), click Reprocess at the bottom of the Console
- Choose what to reprocess (errors only, split array errors or all) and click Continue
- Dobermann resets the selected transactions and re-executes them in the same batch
Reprocess Options
When you click Reprocess, the Reprocess Batch window offers three options:
| Option | What it reprocesses |
|---|---|
| Errors only | Only transactions that returned an error response |
| Split array errors | Splits failed array transactions into individual elements (see Split Reprocess below). Not offered for a paginated batch |
| All | Every transaction including completed ones — a full do-over (asks you to confirm) |
Selected transactions are reset to pending and re-executed within the same batch. Completed transactions are left untouched (except with Reprocess All).
Reprocess One Transaction
For quick fixes — like correcting a single record in your source data — reprocess one transaction without touching the rest of the batch. Any of these works:
- The Reprocess button on its card in the Raw tab
- The Reprocess button in View transaction
- Right-click its row on the Error or Input tab → Reprocess
The transaction updates in real time as it runs, and a reprocess count badge shows how many times it has been reprocessed.
This works during and after a batch run, and on a single Run API transaction too — Reprocess runs it again.
Split Reprocess
When a batch request contains an array (e.g., creating multiple items in one API call), a single bad element can fail the entire request. Split Array Errors breaks each failed array transaction into individual requests — one per element — so you can isolate exactly which element caused the error.
How it works:
- Choose Split Array Errors from the reprocess menu
- Dobermann finds failed transactions that contain array data
- Each array element becomes its own transaction
- The new individual transactions execute automatically
This is useful for bulk data loads where a few bad records shouldn’t block the rest.
Reprocess Count Badge
Each transaction tracks how many times it has been reprocessed. Once it has, the 🔄 on its Reprocess button becomes a numbered badge:
- No badge — never reprocessed
- Badge with number — reprocessed that many times (e.g., “2” means twice)
- Completed transactions that were reprocessed keep the badge on a disabled button
When Reprocessing is Available
Reprocessing is available when a batch has reached a terminal state:
| Batch Status | Available Actions |
|---|---|
| Completed | Reprocess |
| Error | Reprocess |
| Cancelled | Reprocess, Resume |
| Stopped / Paused | Resume (not Reprocess) |
| Running / Pending | Reprocess one transaction only (batch-level reprocess disabled) |
| Paginated | Reprocess (no Split Array Errors) |
Stopped and paused batches show Resume instead of Reprocess, since the batch hasn’t finished yet. A paginated batch reprocesses its failed pages like any other batch: each page runs its own request again. Split Array Errors isn’t offered there, because splitting would change how the next page is numbered.
Related Topics
- Console — Run requests, monitor progress, analyse results
- Batch Preparation — Data loading and column mapping
- Pagination — Configure and run paginated API requests