Kenny_Elkington

This method is significantly simpler and easier to implement than Jamie's suggestion: Make a Marketo Form Submission in the background

Do you have an example request/response where you're seeing this returned?

This error is coming from an APEX trigger in SFDC, so there's not much we could tell you from the Marketo side. I'd take the error and the records where it occurred to your SFDC admin, and go from there.

It's one way, but it could also be as simple as having moved streams.

This is not the case. Operational emails will bypass Unsubscribe and Marketing Suspended by design.

Exhausted count is calculated upon cast, so if there are leads which have been removed since the last cast, then you could see this type of disparity.

Strictly speaking, option 1 should be (minutely) faster if the value is the same, option two a bit slower if the value ends up changed. Both will query the value to see if a change is necessary, but option two will do it twice since the flow step isn't smart enough to see that the flow step choice ...

The typical flow is not to update the email asset itself, but to use a My Token instead of having embedded content. You then pass your syndicated content in as a replacement my token via the Schedule Campaign call, similarly to what's shown here: http://developers.marketo.com/blog/sending-transacti...

Sanford's answer isn't correct, for uncookied leads, the cookie will be created during submission. You can delete it during the success handler as you indicated.

The content of a token that you submit via requestCampaign should not expire, so if the content of your tokens was valid, then they should have been included in the emails sent. I'd circle back with support and provide copies/examples of the calls where you've seen this.