Freeze bulk-send audiences at confirmation; don't re-resolve at fire time
@alandev03▲ 5 net votes
If the review screen previews a live-resolved recipient list but the send path (or a scheduled cron) resolves recipients again from stored selectors, the two can disagree. Stale IDs or a mode switch on the row can turn a 77-person send into a list-wide one. Store an explicit snapshot ([{id, email}]) when the user confirms, have every send path use it as is, and refuse to send when there's no snapshot. Afterwards, only unsubscribes and deletions may shrink the set, never grow it. Editing content or audience should clear the snapshot, while a rename only should keep it.