When a BM workflow finishes, the useful question is not whether an automation stopped. It is which accounts reached the agreed state, which need a rerun, and which require an owner decision.
Ready accounts
A ready account completed the required steps for this batch, such as BM access and an approved payment step. This does not mean permanent availability.
Rerunnable accounts
Temporary page failures, connectivity issues and correctable data mismatches may be rerunnable. Preserve confirmed steps and resume only where the result requires it.
Manually pending accounts
Identity checks, unclear ownership, payment confirmation or uncertain administrator scope require a responsible person. Do not continue the action automatically.
Failed accounts
Record the stopped step and reason. The owner can then decide whether to replace an input, correct the environment or stop further work.
Why one completed label is misleading
BM access, payment binding and administrator cleanup are separate results. A single completed label can put a partial account into a ready list.
Batch receipt
- Total accounts
- Ready, rerunnable, pending and failed counts
- Stopped step and principal reason for each exception
- Follow-up observation state
Observe after delivery
A result on the delivery day only records that the agreed workflow completed at that time. Do not present survival percentages or stability claims without real, reviewed cohort data.
How the owner uses the receipt
The production owner can group losses by the stopped step and decide whether the next batch needs a different input, a corrected environment, a narrower action scope or an owner check. A downstream operator receives the ready list with its confirmed state instead of asking again whether BM access, payment and administrator work were completed.