Live Batch Identification Progress and Recovery
Watch cards finish identifying one by one, and resume a batch that was interrupted instead of watching it spin forever.
- Status
- Shipped
- First discussed
- Development started
- Shipped
- Last updated
Overview
While a batch is being identified, Scan & Identify shows each card's live stage and a running count such as 12 of 50 identified, and the batch page updates without a refresh. If a run is interrupted by a restart or a provider outage, SlabIQ notices the stopped run, explains why it stopped and offers to resume with only the cards still waiting.
Completed work
- Batch pages update automatically when SlabIQ finishes work, with no manual refresh
- Scan & Identify shows each card's live stage and a running identified count
- A run stopped by a restart or outage is detected, marked as stopped with the reason, and its cards return to the queue
- 'Resume identification' restarts only the cards still waiting
Milestones
- Completed
Live updates on batch pages without refreshing
- Completed
Per-card live identification progress
- Completed
Stopped-run detection and Resume identification
- Completed
Concurrent pipeline, per-card trace and batch context
- Completed
Live refresh as cards finish, and restart recovery
What “done” means
The outcomes this item has to deliver, and when each was confirmed.
Scan & Identify shows a live per-card count while a batch is identified
Met
A batch interrupted mid-run can be resumed instead of staying stuck as processing
Met
Batch pages reflect finished work without a manual refresh
Met
Cards appear on the batch page as they finish, without a manual refresh
Met
A run interrupted by a restart can be resumed and does not leave cards stuck processing
Met
Development updates
No development updates have been posted yet.