Jon_Wu

Hi Josh. Not sure I follow. Are you saying that maybe I could prevent the decrement from happening if I could tell that events were being replayed during association?Even if I could prevent it from happening at that moment, I'm not sure how I would actually decrement the score by the appropriate amo...

Hi Sanford. It seems like what I have down gives some balance between adding a little safety and not increasing complexity too much, adding external dependencies, or slowing down performance by more than a couple hundred ms, but I'd love to hear more about your thoughts on compare-and-swap via webho...

Thanks for the advice! While normally, I think readability is king, I was opting for the positive lookup to go along with the Smart List Best Practices #3:Use positive over negative operators - While "not" filters are available, they have to search the entire data set in your instance, which can be ...

Thanks for taking a look Denise.It reads in a confusing way, but I think it's doing what I want, while avoiding "not it" / negation for the best list querying performance although I haven't had a chance to test yet. The intent is that we don't remove from flow if you're still in the list, then conti...

Seems like without the ability to lock, you basically can't ever implement at-most-once. Outside of Marketo we use Pub/Sub, which has at-least-once delivery as is common with distributed systems, so we have to track each message ID centrally in MySQL with locking to avoid duplicate processing.It see...

Hi Denise,Yes in addition to lack of "locking read" support for exclusive access to the list within a few second time period (much like Sanford is talking about and I'm thinking about as an engineer), I'm also concerned about the gap of time between member list creation and campaign execution (from ...