Skip to main content
Level 2
Aug 19, 2025 9:34 PM UTC
Solved

Salesforce object sync skipping all updates

Hi! Recently we've added 3 new fields as constraints to a Salesforce Object called "Application", since then all the sync operations related to this object have resulted in everyone being skipped.

 

We've checked on Salesforce side and the fields are visible and the Marketo Sync user has all the necessary permissions, so in theory everything should be working. I've tried refreshing the schema but it didn't help at all.

 

Does anyone have any idea what could be causing this problem? We don't get any error messages, everyone is just skipped in any operation related to the Application object.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
GabrielLu3Accepted solution
Level 2
Aug 22, 2025 6:26 PM UTC

So, we reached out to Marketo support and the problem has been fixed.

 

Turns out the sync was stuck and the support team fixed it by moving the watermark date. We still don't know exactly what caused the sync to get stuck,  but we know the problem was on Marketo's side. 

4 replies

SanfordWhiteman
User Group Leader
User Group Leader
Aug 20, 2025 3:36 AM UTC

What’s the exact relationship between this object and the Contact/Account/Lead objects in SFDC?

Translate
Level 2
Aug 20, 2025 12:45 PM UTC

This is a custom object similar to Opportunity, each lead can have multiple applications. It was working fine until we added those 3 new fields as constraints, then this problem started.

 

Translate
SanfordWhiteman
User Group Leader
User Group Leader
Aug 20, 2025 11:11 PM UTC

What is the nature of these 3 fields? Are they lookups?

Translate
GabrielLu3AuthorAccepted solution
Level 2
Aug 22, 2025 6:26 PM UTC

So, we reached out to Marketo support and the problem has been fixed.

 

Turns out the sync was stuck and the support team fixed it by moving the watermark date. We still don't know exactly what caused the sync to get stuck,  but we know the problem was on Marketo's side. 

Translate