hardScenarioDesignMidSeniorStaff
The monthly bill run dies two thirds of the way through and the cycle closes tomorrow. What do you do?
5 min readUpdated 2026-08-15
Answer
Short answer
Restart rather than rerun. The run is not a transaction but a sequence of per-account commitments, so each account must be either fully billed or untouched, charge assembly must be deterministic from inputs frozen at cut-off, and quarantining the offending accounts beats missing the cycle.
Was this answer helpful?
Likely follow-ups
- How do you allocate invoice numbers so a restart cannot consume two for one account?
- One account fails every attempt. What do you tell finance at cycle close?
- A price change was released while the run was in flight. What are the consequences?
- Which counts would you publish from a run so anyone can prove it was complete?
Related questions
- Take me through a bill cycle, then tell me what the invoice looks like when a customer changes plan mid-cycle and disputes the result.mediumAlso on billing and revenue-assurance5 min
- You must ingest all of English Wikipedia every day, and the source does not want to be hammered. What runs, how often, and what do you do about the run that fails at hour six?hardAlso on idempotency6 min
- An Android app queues actions while offline. After the process is killed and restarted, some actions sync twice and the user sees duplicate orders. How do you design the fix?hardAlso on idempotency4 min
- Your services talk through events and one consumer has been down for an hour. What has it missed, and how does it catch up?hardAlso on idempotency6 min