Liliana_Cheng1

Hi Community, this was solved last week. Here is the official response from one of the Marketo engineers who assisted on our support rep:The updates that some customers saw were due a change that was made in the most recent release. This has since been patched and it has been verified that it is no ...

Hey Anthony, yes and you were correct that it was a bug associated with their Q1 Minor release. A shame that we didn't have access to those release notes!

Hi Nichole Cunningham, I'm researching email validation tools for our forms and have the same questions as you did. What are your thoughts on BriteVerify so far?Thanks!Liliana

Hey Anthony Pica, our support rep will escalate our ticket and reference your ticket as well. He looked yours over and said we're having the same issue so he will ask tier 2 to investigate.

Thanks Anthony Pica. I have a case open too and I'll share whatever helpful info they respond with. We were negatively impacted as well because we also have trigger-based email campaigns based on data value changes. Have you turned off your trigger campaign or have you found a workaround to prevent ...

Thanks for your help, Greg. Here's a screenshot of the Minutes to First Contact activity for this example. There are only four activities on the log. The behavior of fields being reset to null, and the behavior of daily sync updates are both brand new behaviors in our instance. We have not seen this...

Hi Scott K. Wilder​, I just passed the Marketo Certified Expert exam on Sunday March 20 14:04:49 MST 2016. Could you please use your magic to update my account as well? Is there a way to do this myself?Thanks.

Hi Amanda Wobrock, we have a similar issue with a large backlog on the account sync and delayed triggered emails. Do you guys have something integrated with Salesforce that updates account records? Have you pulled a Salesforce report to check last modified accounts and which user is making the most ...

Thanks Sanford Whiteman. Your explanation makes sense for the most part. The form was split up into a multi-step form, so each step appended #step-1 to the URL. This is relatively new for us, so that's probably why we hadn't seen this issue previously. The other versions of our multi-step forms have...