Aaron_Dear

Story of my life. GTW is infamous for 403 errors. A launchpoint re-auth is all it takes to "fix" it until a week later.

Hey Amanda! Answers below:Did the leads exist in SFDC before being associated to the program/event? Nope. They were sourced from a form fill out in Marketo.I have come across the scenario that if sync fails on the first attempt (the attempt to create a lead in SFDC), it won't try again, and you have...

Ah, excellent. So I could absolutely do this then. Thanks Sanford!

Would be quite nice to see how people are implementing this directly into a Salesforce view - without the use of MSI.

True - perhaps the log line for the error is all that it's displaying. That said, it's still blocking the sync to Salesforce.I looked in a bit more, and only got more questions. For others who run into this issue and are frantically Googling to get through it:We currently update this custom lead sou...

Are you still getting this error? We are too!The Salesforce record doesn't have the "\n". The Marketo record doesn't have the "\n". But the error message notes that the field's value has an "\n". So odd.I'm about to delve into a related Salesforce flow that might be culprit. This link talking about ...

The syncing had been almost a black box for me, until I read through Edward Unthank's amazing breakdown. There's one paragraph that's pertinent to your exact situation here.Long delay between Marketo and SFDC?"Timeliness of sync between Marketo and Salesforce"Sync lead to SFDC" and "Add lead to SFDC...

Yep, I've got that same question. It's unfortunate, but I'm OK with a custom service if it means getting my data corrected!