Steven_Vanderb3

You'll want to check your workflows in Salesforce. If a duplicate is being created by "SF Operations", it suggests something in Salesforce is causing this. To Marketo, it looks like a net new record so it's just syncing it down.

When the engagement program casts, it selects the next piece of content in the stream that the person should receive. It's either a single email or a single smart campaign. That smart campaign can has as many flow steps as it needs to accomplish what's appropriate for the cast, but the design of eng...

You can purchase additional daily quota of API calls by contacting your customer success manager. But the concurrency rate and the rate limit will not be increased under any circumstance.

Marketo doesn't support History objects; unfortunately it doesn't stop you from trying. Disable your Event History objects from syncing in the SFDC Custom Object menu in Admin and the errors will go away.

Someone filled out the form by navigating directly to the page rather than clicking a link in an email. Pre-fill only works with links that contain mkt_tok values, and those come from emails. I've seen this configuration cause so many issues (especially in scenarios where emails are forwarded to oth...

Are you an admin of the instance? If not, you'll need to reach out to your admin because it sounds like your user does not have permissions to edit templates.

POST-ing directly to /save2 is unsupported and is not guaranteed to work in the future. I would advise not going this route.

The list will upload to the partition set as the default for that workspace. You can't specify it past that, but you can migrate them after upload via a smart campaign or list action.

Please file a support ticket. Mention that you need to be able to use the "updatedAt" parameter in the bulk API and they'll have it provisioned for you (if it's not already). It's no additional cost.

Can you go into more detail about what issue is? Is there an HTTP error? Some other type of error that gets displayed on the page? If Support cannot replicate by taking the same steps, I would hesitate to assume it's caused by a draft issue.