Date trigger automation not running - can't explain?
Hi there - wondering if someone has come across this and has advice. I have an automation (several actually, but all similar) set up with a Date Trigger. Specifically set to run 1 Day After the Date Field (e.g., 1 day after Last Connection Date). Idea being to create a reminder activity to reach out.
Thing is, it never runs.
All other criteria are being met, and it is active for me.
My only hypothesis is that the 1 Day After is an exact thing, i.e. it only runs if the Last Connection date is "exactly" one day ago. Not one or more. This poses a challenge as I need to be able to look back at all People and all Last Connection Dates to trigger set up of various reminder activities. And, for most people the Last Connection wasn't only 'one day ago'
Am I misunderstanding how the Date Trigger works? Is there a different/better way I should be going about this to make it work?
Thanks
Answers
-
Hi @shapiroja , can you please share a screenshot of how your automation was set up? That will help us better understand all the steps and where it could not be going as expected.
0 -
Here you go…
I would expect, when this runs at 8:15, it would find any People whose "Last Connection" was more than 1 day ago then based on filters create the activity…But it doesn't trigger at all.
And nearly every Person has a Last Connection earlier than one day ago.
0 -
The date trigger itself seems to be set up fine. But is the filter used in the automation condition shared with all users who trigger the automation?
0 -
Hi @Manuel Oliveira and @mac@datomni.com - just wanted to reach out and see if you had any additional thoughts/direction? This is a pretty fundamental challenge we're finding and welcome any thoughts you might have on how to resolve… or other direction we might take…
Thanks
0 -
Hi @shapiroja,
another thing I’d check is the trigger itself. Looks like you’re using the (custom?) Last Contacted field—it should be a custom date field in the
yyyy-mm-ddformat (ISO 8601). For example, the default Pipedrive'slast_activity_datefield stores values in the format2024-11-11. Make sure your custom field uses the same format.0 -
Thanks @mac@datomni.com - I do believe it does (it was selected as a Date custom field - I assume that's the format?). Is there a different way to confirm?
Would certainly be easier to use last activity, however we created this field because pipedrive treats activities and emails (from email sync) separate, despite them both being 'connections'…
Appreciate the support!0 -
@shapiroja We replicated this automation using a newly created Date custom field and a standard field. It triggered correctly in all cases for the Exact Day scenario (screenshot attached). There's no reason to think it wouldn't trigger if the last activity, recorded in either the default or custom field, was actually 1 day ago.
The automation logic appears to be correct, so this seems to be a data issue. I recommend checking all dependent automations to ensure they properly populate this custom field with data before that daily activity automation runs. If you'd like us to audit this, ping me a PM, and we'll be happy to take a closer look.
0 -
Very odd @mac@datomni.com. I've verified the format/setup of the customer variable…seems right (as best as I can tell). For us, given we're not yet in a 'steady state', I'm trying to use the date trigger to capture things that are '1 or more' days…thinking the After Date = 1 would run through anything whos date is more than 1, not exactly 1 (perhaps I'm wrong, but it's also not triggering on things that are 'exactly 1 day ago'.
Welcome the opporutnity to dig deeper with you, if you're willing. Will PM. Thank you!
0
