Keep an AI Batch Request From Hiding Individual Failures

A batch task is complete only when every required item reaches the intended state. A message saying “processed the batch” can conceal missing or failed items. Give each item an identifier and a visible status.

Try a bounded example

For a fictional set of ten public notices, record Drafted, Reviewed and Published separately. Keep the destination reference beside the status when available. Do not mark all items published because the first notice opened correctly.

Define the checks that apply to every item and the checks that apply to the batch. Each notice needs correct facts and a valid destination. The batch may also need unique titles, no missing dates and no accidental duplicates.

Check before accepting

When one item fails, preserve its error and continue independent work where appropriate. Do not silently replace it with a different item merely to keep the total count correct. Reconcile the manifest with the real destination before retrying.

Finish with counts that add up and a list of remaining items. A local file, a draft and a confirmed public result are different states. Honest item-level tracking makes continuation safer and prevents the next session from repeating work that was already completed.