The Mailchimp entry supports workflows where batch processing is useful, but the batch itself is not one indivisible success. The asynchronous batch guide explains that operations are not guaranteed to run in order.
Assign operation identifiers, wait for completion, and inspect errored_operations plus each operation's result. A finished batch can still contain failures.
Do not put dependent steps in the same batch and assume sequence. Retry only the failed work after checking its current state, and preserve subscriber preferences rather than treating a technical retry as permission to change consent.
Akousa