I’ll also add that when I look at the analytics, it doesn’t even show any profiles in waiting:

Hi ​@DanaC! Thanks for posting – I understand how frustrating this can be. I believe the problem here is that there is a glitch in the system where a trigger cannot calculate a time related to an established property. For example, I tried to set up a flow to send a discount code to a customer on the anniversary of their first purchase. In order to set it up, the trigger had to be “Customer places first order” and then add a waiting periods of 365 days. The trigger would not work for “1 year after first order date” because it requires the flow to be calculating times before the trigger has been activated. This may have changed since I set up the anniversary flow because it let you set up that trigger start time to begin with, but it would explain why there is no one on the waitlist and it has not worked so far. 

My recommendation would be to create another date property that is 5 days prior to the cscope property, then have that be the trigger. It would require more manual labor on your end to make sure that this new property was up-to-date but I believe it would fix the problem.

Let me know if you have any other questions or if/how you figure out the fix!

Hi ​@DanaC,

I wanted to reach out to let you know that this is appears to be a bug that our engineers are working to fix. I know you’re looking for a specific date for when this will be resolved, or information regarding the reason for the bug. As of now, we’re still investigating this, but will do everything we can to help you figure this out! Apologies for any inconvenience this is causing.

-Byrne

Hi Bryne,

Thanks for the response. I’ve been doing all kinds of testing and it also looks like that if a profile isn’t queued up 24hrs before it’s supposed to be sent, it doesn’t work at all. So if the flow is set to execute at 8am the next day but the profile is added 10 hrs before, that user will not get the SMS. Can you confirm this on your end?

If this is the case (as all of my testing indicates), I’d say this is yet another major flaw. Was this date field just recently rolled out? I’m wondering how this managed to get to production in this state?

Thanks,

Dana 

Hi ​@DanaC,

When a profile has a date property added or updated, Klaviyo runs a check to see if they’d enter all date-triggered flows in your account. If a profile gains a date property 10 hours before they’re to receive an SMS in a date-triggered flow, they will enter the flow and receive the message, as long as they’re not filtered out by any flow filters. Our article on how date-based flows schedule recipients explains this in-depth.

Date properties and date-based flows have existed in Klaviyo for quite some time now, and in general, are not especially prone to bugs or issues. That being said, when an occasional issue does arise, like in your case, our team works hard to fix them as soon as possible.

-Byrne