Supposedly, if your DB size is greater than 1M records, Marketo automatically moves you to this so called enhanced architecture (that's ultimately related to Project Orion) - called "Corona". We didn't even realize we were on it until several critical issues with our data surfaced this week - and reaching out to Support confirmed Corona could be the culprit (major delays in processing smart lists and smart campaigns). The other question we're waiting to hear about is why we were even placed on Corona - since our DB size is less than 200,000 records. Here's an example issue that we uncovered this evening:
I just ran a single flow action ("change data value") against a set of 96 email addresses (11 of those leads had their country properly defined, but I left them in here anyway since they would just be skipped) . All I did was populate the country value (to Brazil) of any lead that had a missing country value. The flow action completed successfully – and if you access the lead record of any of the leads, you can see that the country value is indeed “Brazil”. Yet when I view the leads at once, many have NULL country values:
When clicking on any of the lead records here, the “country” value contains Brazil - it's just not showing up properly in the leads view. Also, if you add another filter to the smart list – [where country is “Brazil”], it will only return the following 11 leads (out of the 96 that actually have "country = Brazil" in their lead record - these are the leads that weren't affected by the "change data value" flow action that was just applied; and already had "Brazil" as their country value):
After contacting support, it was uncovered that our instance was moved to Corona and that they are experiencing a significant lag in showing data properly (as I'm writing this, it's been two and half hours since running the flow action to change the country value of all leads to "Brazil" - and it still looks like the first screenshot above). This isn't just a display issue. As noted above, filters/triggers in smart lists/smart campaigns don't have access to this updated data either. If that's the case, I can’t even imagine the magnitude that this issue is causing in our environment – and how leads are not being processed correctly.
Just wondering - has anyone else experienced issues such as this?
Unless you've added them to a My List 
Dan Stevens thanks for bringing this to our attention. Can't say I've come across anything so far but will now be keeping an eye out as I believe we're on the upgraded architecture.
Hi Chris - this isn't really focused around any so-called lag or delay in how the platform performs. The issue here is really focused around any of your smart lists or more importantly, smart campaigns where specific flow steps are expected to happen. For us, the issue is mainly around any time a lead that had/has a "change data value" occur of any field - while it's reflected in the lead record, the smart lists/campaigns aren't able to filter/trigger off of it. Let's take the following example:
- We have a series of Engagement Programs built that contain offering-specific content
- We have an "Add to Engagement Program" trigger campaign in each EP that listens for the following, and then adds those leads that qualify to the EP:
- The key trigger here is the "Area of Interest" code. Many of our Marketo programs are aligned to our offerings. When we see someone engage with content aligned to one of those offerings, we give them this area-of-interest code - in this example, "DB-DC".
- Leads that acquired that code (through a "change data value" flow step) - as a result of achieving success in a related program - are not being seen (not qualifying) within this smart campaign. So they're never added. This is just one example.
This is what I was referring to as the "lag". While the value may exist in the lead record, the value is not made available to filters/triggers for days/weeks. At least that's what we found out after doing some further investigating of this issue. And therefore, this has affected hundreds of our existing trigger campaigns that have been setup to process leads properly (e.g., country lead partition routing; lead lifecycle campaigns; adding leads to EPs; etc.).
While I did get an update this morning that the issue was fixed by re-indexing our DB - and that Marketo engineers are creating a patch for the issues on Corona processing for customer smart lists/smart campaigns - we're still left with all of these smart campaigns that didn't process as they were designed to.
UPDATE (10/20/2016): Unfortunately, the re-indexing of our DB did not fully resolve this. It has resolved some of the list/smart list issues, but our trigger campaigns still aren't firing when they should be.
.png)