{"title":"Resolve email bounce sync errors","slug":"resolve-email-bounce-sync-errors","url":"https://support.storeconnect.com/articles/resolve-email-bounce-sync-errors","url_markdown":"https://support.storeconnect.com/articles/resolve-email-bounce-sync-errors.md","subtitle":null,"summary":"Fix EMAIL_ADDRESS_BOUNCED and INVALID_EMAIL_ADDRESS sync errors caused by bounced contact emails, DKIM misconfiguration, or email sending limits.","type":"Help_Documentation","video_url":"","keywords":"EMAIL_ADDRESS_BOUNCED, INVALID_EMAIL_ADDRESS, bounce, DKIM, email, sync error","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"## Symptoms\n\nYou see a sync error in the [sync error tool](sync-error-tool) with one of the following patterns:\n\n- **EMAIL_ADDRESS_BOUNCED** — \"The target object email address is currently marked as bounced.\"\n- **CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY** with an inner bounce message — a Flow such as the **Order Builder** process fails because the contact's email is bounced.\n- **INVALID_EMAIL_ADDRESS** — \"Unable to save a record due to an invalid email address.\"\n\nThese errors can also cause password reset and invitation failures on Contact records.\n\n:::tip\nIf you see **EMAIL_TEMPLATE_MERGEFIELD_ERROR**, that is a separate issue. See [resolve email template merge field sync errors](resolve-email-template-sync-errors).\n:::\n\n## Cause\n\nA bounce occurs when an email cannot be delivered, most commonly because the email address on the **Contact** record is invalid, mistyped, or no longer active (for example, a former employee's address). Salesforce permanently marks the contact as \"Bounced\" after a failed delivery attempt, after which it refuses to send any further emails to that address and may block record saves that involve that contact. This causes sync failures.\n\nThe bounced flag persists even after the underlying problem is fixed. You must clear it manually.\n\nOther reasons an email may be marked as bounced:\n\n- **Daily email sending limit reached.** Salesforce has a daily cap on outbound emails. Sends that fail due to the limit are recorded as bounces.\n- **DKIM keys not configured.** Emails fail authentication and are rejected by the recipient's mail server, which Salesforce records as a bounce.\n- **Domain DMARC policy** rejecting emails that lack proper SPF or DKIM records.\n\n## Resolution: email bounce\n\n### Step 1: Clear the bounced status\n\n1. Open the affected **Contact** record in Salesforce.\n2. Clear the **Email Bounced Reason** field.\n3. Clear the **Email Bounced Date** field.\n4. Save the record.\n\n### Step 2: Re-sync the affected records\n\n1. Go to the [sync error tool](sync-error-tool) in StoreConnect.\n2. Select the checkbox next to the affected record(s).\n3. Click the **Re-sync** button.\n\n:::tip\nSelect all records in the list when re-syncing, not just the one that failed. Related events for the same record may also need to be re-processed.\n:::\n\n### Step 3: Investigate the root cause\n\nClearing the bounce flag fixes the immediate error, but if the root cause is not addressed it will recur.\n\n**Check email logs:**\n\nIn Salesforce, go to **Setup** \u003e **Email Log Files**. Look for delivery failures around the time the bounce was recorded.\n\n**Check daily email limits:**\n\nUse [Salesforce Workbench](https://workbench.developerforce.com/) to check your remaining email quota:\n\n1. Log into the org via Workbench.\n2. Navigate to **REST Explorer**.\n3. Execute: `/services/data/v33.0/limits`\n4. Find **SingleEmail** to see the daily maximum and remaining sends.\n\n**Verify DKIM setup:**\n\nIf emails are bouncing due to authentication failure, DKIM keys need to be configured in Salesforce and your domain's DNS. DKIM records are added as CNAME entries in DNS pointing to Salesforce's DKIM endpoints.\n\nFor full email configuration guidance, see [setting up StoreConnect emails](setting-up-storeconnect-emails).\n\n## Resolution: invalid email address\n\nFirst, confirm the correct email address with the customer. Then update the email using one of these methods:\n\n**Via the Sync Error Tool:**\n\n1. Open the sync error in the [sync error tool](sync-error-tool).\n2. Edit the email field directly in the error detail panel.\n3. Click **Re-sync**.\n\n**Via the Contact record:**\n\n1. Open the Contact record in Salesforce.\n2. Update the email address to a valid value.\n3. Return to the [sync error tool](sync-error-tool) and re-sync the affected records.\n\nIf you are unable to obtain a valid email address, you can assign a placeholder address (e.g. a generic catch-all address your team monitors) so the record can sync successfully. This is preferable to leaving the record in a failed state.\n\nIf a Flow or trigger is sending emails as part of the sync and causing the failure, temporarily disable it, re-sync, then re-enable it once the email address is corrected.\n\n## Verification\n\n1. Confirm the sync error no longer appears in the [sync error tool](sync-error-tool).\n2. Confirm the contact's Email Bounced Reason and Email Bounced Date fields are clear.\n3. Place a test order to confirm future orders sync and send emails without issues.\n\n## Prevention\n\n- **Configure DKIM keys during initial Salesforce setup.** This should be part of your go-live checklist. Without proper DKIM configuration, emails may be rejected by recipient mail servers and recorded as bounces.\n- **Monitor email sending limits** for high-volume orgs, especially during peak sales periods.\n- **Use the Sync User exclusion pattern** on email-sending Flows to prevent bounce-related sync failures. See [resolve Flow and trigger blocking sync errors](resolve-flow-trigger-sync-errors) for details.\n\n## Related issues\n\n- [Manage sync errors](sync-error-tool)\n- [Setting up StoreConnect emails](setting-up-storeconnect-emails)\n- [Resolve Flow and trigger blocking sync errors](resolve-flow-trigger-sync-errors)\n- [Resolve email template merge field sync errors](resolve-email-template-sync-errors)\n- [How to find and resolve sync errors](how-to-find-and-resolve-sync-errors)"}