Follow a batch and read its result

What the progress counter counts, what happens if you close the page, and how to read a batch that only half worked.

A batch is a queue of independent jobs, one per piece. Reading its progress correctly saves you from the two mistakes that cost money: running it again, and assuming it failed.

The block you will be looking at

This is it, with a batch half done — the bar, the two counters, one row per piece with its state, and the two buttons this page is about:

Your jobs are in progress

66%

Processed: 0 of 0

Completed Jobs: 2

Failed Jobs: 1

Job Status Details
List · Zoide Nº 7 · #12 done Listed at 0.0250 BSV
List · Zoide Nº 7 · #13 running Building the transaction
List · Zoide Nº 7 · #14 failed Not yours any more — skipped
The jobs block, with a batch in progress. Rows and figures are made up; the block is the real one.

What the counter counts

Pieces finished out of pieces asked for, updating on its own without you reloading.

Finished means the job for that piece is done — its transaction was built, signed and broadcast. What it does not mean is that every index in the world already shows it. A batch can be complete while your wallet still shows a piece or two the old way for a few minutes.

You can close the page

The jobs run on the server, not in your tab. Closing the page, losing your connection or going to sleep does not stop them. Come back to the Bulk Manager and the state is there.

What you should not do is start the same batch again because the tab was closed. Those pieces would be processed twice, and each attempt costs its fee.

Stopping a batch

You can stop one in flight. Stopping is honest about what it can do: work already sent to the chain is done and stays done. What stops is everything not yet started.

So a stopped batch normally leaves you with some pieces processed and some not. The jobs block tells you exactly which.

Reading a partial failure

When some pieces fail, you get the list of failures with their reason, and everything that worked stays committed. No rollback.

The usual reasons, in order of how often they happen:

  1. The piece is not yours any more — sold or transferred between building the selection and running the batch.
  2. Not enough funds for the remaining pieces. The fee is per piece; a batch can run out halfway.
  3. The piece was already in that state — already listed, or not listed when delisting.

None of these need anything undone. Fix what applies and run a new batch with just those pieces.

Clearing the block

Clearing does more than tidy up: it re-reads the chain and rebuilds your selection from what is actually true now. Pieces that left your wallet show up greyed out instead of silently vanishing, so you can see what happened rather than guess.