Sync Lead to SFDC Caught Exception – Fail to Reset Contact | Community
Skip to main content
PeeyushSachdeva
Level 4
April 21, 2026
Question

Sync Lead to SFDC Caught Exception – Fail to Reset Contact

  • April 21, 2026
  • 2 replies
  • 16 views

Hi All,

 

I'm running into a sync issue between Marketo and Salesforce and would love some guidance from the community.

 

Issue Summary:
A person record in Marketo is failing to sync with Salesforce and throwing the following error in the activity log:

  • Fault: Sync Lead to SFDC caught exception
  • Exception Message: Fail to reset Contact <Marketo Person ID>

The record was deleted from Salesforce but still exists in Marketo with the associated SFDC ID attached.

 

Has anyone encountered the same issue?

 

Any guidance, workarounds, or similar experiences would be greatly appreciated! Thanks in advance. 

    2 replies

    SanfordWhiteman
    Level 10
    April 21, 2026

    Have you tried running Delete from SFDC (yes, even though it's already deleted on the other side).

    PeeyushSachdeva
    Level 4
    April 21, 2026

    @SanfordWhiteman, Yes, that was actually my first instinct, I attempted the "Delete Person from SFDC" flow step as an initial troubleshooting step, similar to the approach we typically use when resolving "Invalid Cross Reference Key" errors, where forcing the action helps re-sync the state between both platforms.


    However, at the time, my SFDC access had expired, so I was unable to verify whether the Contact deletion in Salesforce had successfully synced back to Marketo. That was the assumption I was working with that the deletion may not have properly reflected on the Marketo side, which is why I tried that flow step first.


    Once I regained SFDC access and investigated further, I confirmed that the record was indeed fully deleted in Salesforce but still existed in Marketo with the old SFDC ID intact which is when the "Delete Person from SFDC" action stopped being a viable option.

    SanfordWhiteman
    Level 10
    April 22, 2026

    Hmm. Try to create a new person and merge this person into it. If that doesn't work, time for a support ticket.