Resolve quarantine discrepancies between marketing and mid-sourcing instances in Adobe Campaign
The marketing instance shows more quarantined email addresses than the mid-sourcing (RT/MID) instance, creating inconsistencies in quarantine records. To resolve the issue, review quarantine sources and validate synchronization processes between instances.
Description description
Environment
- Product: Adobe Campaign Classic v7
- Console Build: 9349
- Server Build: 9349
- Instance: Production
Issue/Symptoms
- The marketing instance contains quarantined email addresses that do not appear in the mid-sourcing instance.
- Several quarantined records lack a Last Occurrence date or delivery details.
- There are no corresponding delivery logs or documented reasons for quarantine in these records.
Resolution resolution
Follow these steps to address the issue:
- Review how quarantined addresses are added to the marketing instance. Refer to the Understand quarantine management documentation.
- Check for manual entries, imports, workflow automations, migrations, or synchronization processes that directly add addresses to quarantine.
- Confirm whether bulk imports or integrations populate quarantine records outside standard automated flows.
- Ensure SQL rules are not used to assign quarantine status; only delivery errors or explicit imports/migrations should do so.
- Examine internal jobs or workflows for possible bulk addition of quarantined records.
- Compare marketing and RT/MID instances to identify if specific channels (such as batch emails or past workflows) contribute additional quarantines on the marketing instance.
Related reading
Mid-sourcing deployment in the Campaign Classic v7 Documentation
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f