Salesforce.com sync errors - hundreds of duplicate leads created in SFDC by Marketo user

[Anonymous]

I've been assured in my support case and from other Marketo contacts that the issue is now being handled as a "major priority." I hope so!

Also, I just spoke with an SFDC consultant who wondered if the issue may be related to some Salesforce1 changes to the API, which could have affected Marketo’s API integration for the bidirectional sync with SFDC. Hopefully Marketo devs are investigating that angle, too.

[Anonymous]

Hi Gabe, to address your question is anyone using SFDC integration not seeing this issue. To my knowledge (and I have searched open support cases) the only users who have logged cases similar to this scenario are involved in this community discussion.

[Anonymous]

Thanks, Cathal.

A question for other affected users: Do you also have RingLead installed in your Marketo instance? 

Marketo support is now suggesting that it may be the culprit, though I still don't see any evidence of that since (A) RingLead support has confirmed no errors in my account since 11/14, and (B) my RingLead account is tied to my own username in SFDC, and all the dupes in SFDC were created by my Marketo User.

RingLead was working fine before night of 11/20.

[Anonymous]

Is it a specific type of sync or smart campaign that's causing it? For example, every night I have a smart campaign that auto-assigns unowned leads to owners, thus syncing with SFDC. Most of my duplicates seem to be coming from that.

[Anonymous]

I don't have a Smart Campaign that does a specific sync like that, so it's just the general sync that is broken for me.

[Anonymous]

Good news: The issue seems to be resolved, and it turns out that it was likely related to RingLead, which we have installed in Marketo, and not directly caused by Marketo after all.

RingLead doesn't know why the issue occurred last week or when it was fixed, but for now, my snyc appears to be functioning as expected.

[Anonymous]

I also got notice of resolution, but, as we do not have RingLead, I don't think the bigger problem was due to that.

[Anonymous]

No notice here yet

[Anonymous]

Ann & Bentaacular: Are you still seeing the issue occur?

[Anonymous]

Since I've used up all my api calls for today from de-duping, I would need to wait until tomorrow once it has reset. I have run into instances when I've tried to merge leads and a prompt says that lead has been deleted. So what's going to happen? Is that extra lead just going to sit there forever?