MKTO - SFDC Sync Credentials Password Refresh | Community
Skip to main content
A
Anonymous
August 22, 2013
Solved

MKTO - SFDC Sync Credentials Password Refresh

  • August 22, 2013
  • 2 replies
  • 1092 views
A couple of months ago, our MKTO-SFDC sync failed because SFDC executed a forced refresh of the password for the account we are using to sync. It was a over a weekend so a few hundred of our leads needed to be batch processed the following Monday to get them all synced-up again.

My question: Is there a way/process on the MKTO side that I can implement in order to prevent something like this from happening again? I am sure a lot of your customers on SFDC have experienced something similar.
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
Hi Michael,

Any updates that are synched via the background sync (normally every 5 mins) will always start off where they last finished. 
So imagine you has a successful sync on Friday at 3pm, then a sync failure at 3.06pm on Friday due to an invalid password, you don't realise there is a problem until Monday and you change the password on Monday at 9am.Vverything that failed between Friday at 3.06 and Monday at 9am will be processed.

What you will have to catch up on are any SFDC flow action in your Marketo campaigns that would have been processed in that down time. Any Sync Lead to SFDC actions, create task, add to SFDC campaign etc. 

The best option would be to clone you campaign to create a batch campaign that uses the filter equivalent of your trigger and involve an time constraint.

Password expiration periods can be set in SFDC so that the likelihood of this occurring is lessened.
http://community.marketo.com/MarketoArticle?id=kA050000000L3ddCAC

You might want to vote for or leave feedback on the following idea:
http://community.marketo.com/MarketoIdeaDetail?id=08750000000HciFAAS

Cathal


2 replies

A
Anonymous
Accepted solution
August 22, 2013
Hi Michael,

Any updates that are synched via the background sync (normally every 5 mins) will always start off where they last finished. 
So imagine you has a successful sync on Friday at 3pm, then a sync failure at 3.06pm on Friday due to an invalid password, you don't realise there is a problem until Monday and you change the password on Monday at 9am.Vverything that failed between Friday at 3.06 and Monday at 9am will be processed.

What you will have to catch up on are any SFDC flow action in your Marketo campaigns that would have been processed in that down time. Any Sync Lead to SFDC actions, create task, add to SFDC campaign etc. 

The best option would be to clone you campaign to create a batch campaign that uses the filter equivalent of your trigger and involve an time constraint.

Password expiration periods can be set in SFDC so that the likelihood of this occurring is lessened.
http://community.marketo.com/MarketoArticle?id=kA050000000L3ddCAC

You might want to vote for or leave feedback on the following idea:
http://community.marketo.com/MarketoIdeaDetail?id=08750000000HciFAAS

Cathal


A
Anonymous
August 22, 2013
thank you cathal.

by "sync" i meant it to include the actual push of the lead from mkto to sfdc.
hence, when the "sync" failed, a few hundred new leads didn't get push to sfdc

anyway, thank you for providing that link for setting up sfdc password policies
that should mitigate future issues like this one
Terms & ConditionsAccessibility statement

Loading footer...