SalesForce Sync Error | Community
Skip to main content
Nora_Slattery3
Nora_Slattery3
Level 4
May 3, 2013
Solved

SalesForce Sync Error

  • May 3, 2013
  • 3 replies
  • 1513 views
Hi!

What is the best way to track back to the cause of a temporary SFDC sync error?

I had one occure a couple of nights ago, it hasn't persisted but I am genuinely curious about why it has happened. Any ideas?

Warm regards,
Nora Slattery
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amber_Hobson
I know that ours happened twice because we reached the maximum number of API calls for our SFDC instance. It took us a long time to figure that this was why it had happened, but we noticed we had a high number for the last 24 hour period and were able to figure it out that way.

3 replies

Amber_Hobson
Amber_HobsonAccepted solution
Level 8
May 3, 2013
I know that ours happened twice because we reached the maximum number of API calls for our SFDC instance. It took us a long time to figure that this was why it had happened, but we noticed we had a high number for the last 24 hour period and were able to figure it out that way.
    A
    Anonymous
    May 3, 2013
    Hi Nora,

    I checked the error log for your instance.. Amber's guess was correct you have hit you salesforce.com API limit a number of times over the past few days.

    The SFDC API limit is a rolling 24 limit meaning that if use 100 API call now at 5pm I should get those 100 calls added back to my limit at 5pm the next day, this is why it might seem like the error is coming and going.

    When the sync fails due to insufficient API calls the sync picks up where is left off once the API calls are available again meaning that the background sync should not skip any records.

    For more info: https://community.marketo.com/MarketoArticle?id=kA050000000Kyr6CAC


    Rgs,
    Cathal

    A
    Anonymous
    October 9, 2014
    Cathal, do you know of a reporting method that would expose only sync errors?
    Terms & ConditionsAccessibility statement

    Loading footer...