SOLVED

List of common SFDC sync errors?

Go to solution
Highlighted
Anonymous
Not applicable

List of common SFDC sync errors?

I'm curious if anyone has, or has seen, a list of common Salesforce sync errors/Notifications? Product documentation only lists 1 ( Not Allowed: Salesforce campaign contains incompatible statuses.) and I'm aware of permission errors, but are there any others that are common?

Thanks in advance!

Tags (2)
1 ACCEPTED SOLUTION

Accepted Solutions

Re: List of common SFDC sync errors?

In that case the two you'll see most frequently are

  • Warning: Salesforce Sync Change
    • when a field's picklist values are changed or adjusted in SFDC and the field is used in Marketo,
  • Error: UNABLE_TO_LOCK_ROW
    • When Marketo is trying to edit a lead at the same time as a user is in SFDC

Occasionally, you'll see an error about not being able to sync a lead over because it's behavior score is too high for the SFDC field to handle (means your Marketing team hasn't cleared their cookies in a long time . You can hardcode their score back to 0 and you'll be good to go again.)

View solution in original post

10 REPLIES 10
Highlighted

Re: List of common SFDC sync errors?

Hey Melissa,

I don't have a list handy but can pull it together if necessary. What's your use case?

Andy

Highlighted
Anonymous
Not applicable

Re: List of common SFDC sync errors?

Hey Andy,

No need to put something together - was hoping there might be a doc floating out there with "most common" errors. I have the API error list from Salesforce, just trying to get an idea of which ones people see most for team training purposes

Re: List of common SFDC sync errors?

In that case the two you'll see most frequently are

  • Warning: Salesforce Sync Change
    • when a field's picklist values are changed or adjusted in SFDC and the field is used in Marketo,
  • Error: UNABLE_TO_LOCK_ROW
    • When Marketo is trying to edit a lead at the same time as a user is in SFDC

Occasionally, you'll see an error about not being able to sync a lead over because it's behavior score is too high for the SFDC field to handle (means your Marketing team hasn't cleared their cookies in a long time . You can hardcode their score back to 0 and you'll be good to go again.)

View solution in original post

Highlighted
Anonymous
Not applicable

Re: List of common SFDC sync errors?

These are great - thank you!

Highlighted

Re: List of common SFDC sync errors?

Hi Melissa,

There are quite a few others, such as

  • SFDC Validation rules violation
  • Missing mandatory lead field values
  • some times, more complex ones, such as errors caused by an SFDC trigger trying to update other fields.

In fact, from my experience on about 40 projects, unability to lock rows are very rare, and can only happen in a very specific environment.

-Greg

Highlighted

Re: List of common SFDC sync errors?

I've just had good luck avoiding most of those then! I think I've gotten the missing mandatory field very rarely but also because we don't even try to sync them over unless all of the minimum requirements have been fulfilled.

Highlighted
Anonymous
Not applicable

Re: List of common SFDC sync errors?

I agree with you Andy. It may be more than luck, May be you have implemented smart campaigns in Marketo pretty well.

Rajesh

Highlighted
Anonymous
Not applicable

Re: List of common SFDC sync errors?

Hi Gregoire,

I realize I'm resurrecting an old thread...but your comment regarding the "Unable to Lock Row" sync error caught my attention:

"In fact, from my experience on about 40 projects, unability to lock rows are very rare, and can only happen in a very specific environment."

Under what circumstances/conditions would this type of error be generated? It's an odd one...I haven't come across it before. But we're seeing this error happen every few days. It typically affects up to a handful of records at a time...but recently, we saw 200+ records affected by this sync error...which is why I'm researching it now.

Highlighted

Re: List of common SFDC sync errors?

Hi Eric,

I really takes that an SFDC record be updated by 2 apps or 1 user and 1 app at the exact same time. The likeliness of this to occur is very limited, unless your process spans across multiple applications that work synchronously with the same records.

Can you describe a little more your environment and processes?

-Greg