Kyle_McCormick

Hi Kerry Risley,As others have mentioned before, I would use {{system.dateTime}} to set the date in the flow. This will set the time stamp to have the exact date and time it was filled in. Then in the smart list, you have two options. The easy way is to use the "in future: 24 hours" filter. Whil...

One thing we do to get around this is to add a "Date of Activity" constraint to some of our triggers. This way the trigger will stop processing after a certain date and then we ether deactivate or update it at a later date. This doesn't really help much for emails, but this is our current work aro...

Our process is very similar to yours. It could very well be something else that's causing the delay, however I have found that deleting triggers and filters in the smart lists seemed to fix it. I've been wanting to ask support, but I can never seem to replicate the issue when I want it to occur.

I have noticed this quite a bit when cloning programs or batch campaigns lately. I typically delete the filters in the smart list and re-add them and the leads will usually show up as qualified leads. Not sure if you're cloning or not, but that is usually what is happening to me. Hope that helps. -...

We use SFDC validation rules that blocks updates to Lead/Contacts with a domain that matches our domain. It could probably be expanded to run based on company name as well, but we use it only for domain.

We are creating a 3 email drip campaign. The first email we send will be pushed by us, but then email 2 and 3 will be sent a week after the lead clicks the link in the email. We have tried adding a wait step in the flow, however it doesn't seem to fire correctly.

I had originally thought in Past Before, but unfortunately it is not an option for this trigger. We are just trying to use this as a small drip campaign until our nurture engagement programs are up and running.