We have been struggling with backlog issues because of our large number of pull updates from SFDC. Account pull updates are our largest culprit which then causes issues with the contact pull update backlog, etc. We recently upped our daily API calls to 30K per day and that did seem to help our backlog catch up but am looking for any advice other users have on the right # of API calls per updates. Our biggest customer product that syncs to SFDC just finished updating in SFDC and my backlog for account updates is over 20K and I'm worried that the backlog will build back up. I don't know enough about the API call to "pull update" ratio. Is there any documentation on this, or does anyone have their own experience to share. We're working on combatting the large volume of Account updates by removing fields from the sync user but I'm still just curious to learn more. Every support rep I've talked to seems to have a slightly different take on our issue and it seems to be some sort of black magic knowledge I can't get my hands on. Anyone with backlog issues, resolutions, API call knowledge bombs? Also, if you want access to your backlog vote up this idea like me!
... View more
Customize up to 8 badges at the top of your trophy case for all other Community members to see!
Contributor
Earned on 2.15.21
Earned by 275 people
Select to learn more
Originator
Earned on 2.15.21
Earned by 21 people
Select to learn more
Coach
Earned on 2.15.21
Earned by 86 people
Select to learn more
Ignite 1
Earned on 2.15.21
Earned by 3230 people
Select to learn more
Give Back 1
Earned on 2.15.21
Earned by 3211 people
Select to learn more
Affirm 1
Earned on 2.15.21
Earned by 549 people
Select to learn more
Shape 1
Earned on 2.15.21
Earned by 637 people
Select to learn more
Ignite 10
Earned on 2.15.21
Earned by 246 people
Select to learn more
.png)