If a batch including constituents is created, but before it is committed, a solicit code gets onto a constituent record, then that row goes to exception, with the error "Solicit Codes cannot be deleted via batch".  This happens quite often for us, because we are encouraging the regular collection of email consent opt in.

Support have confirmed this is not a bug. The error message is a confusing one, as it says "Solicit Codes cannot be deleted via batch" even though no solicit codes have been deleted in the batch- they just only exist on the constituent record and not in the batch.

It would be good to either have a better error message that explains the work around ["Solicit codes for this row have since been updated on the constituent record- please delete all solicit codes of type xxx from the solicit code pop up window in this row in the batch to proceed"].

Or even better, fix the batch to handle this scenario- especially if the solicit codes in the batch do not contain any updates.