Kenny_Elkington

My Guess is that "AddLeadAction" needs to be part of your URL/Path, and not part of the body.

Yes, it should be valid for all leads.

Is lead ID 1 a valid lead?

If you create a new custom service and use those credentials, do you have the same issue? Beyond that, I'd suggest you open a support case and include examples calls/responses where you've observed this.

It's possible. Are you submitting the identity request and rest request to the same host, e.g. aaa-999-aaa.mktorest.com? If the hosts are different you'd see what you're describing

Typically when I see this happen, it's because the code doesn't actually replace the previous access token after reauthenticating, it simply passes the old invalid one. Have you checked your logs to compare the the access_token values which are passed before and after encountering the 601 in your c...

Hey Kurt,Your confusion is justified, and we haven't done a great job of communicating what the updatedAt field actually reflects, versus what our APIs use to determine if a record has been changed within a date range. The updatedAt field only reflects changes made to the specific primary Lead/Cont...

Nope, there's no practical limit.

My guess would be that your MSI configuration is incorrect. Take a look at the appropriate setup guide and follow the instructions to reconfigure your MSI in SFDC.Enterprise/Unlimited Edition : Configure Marketo Sales Insight in Salesforce Enterprise/Unlimited - Marketo Docs - Product Docs Professi...

Ah, the problem is that you have your edge linked to Leads. That's not a valid configuration. Your edge needs to not have a link field in order to be a valid link object.