We’ve been having issues with some deal-based workflows generating duplicate auto-tasks when we have re-enrollment turned on. We don’t want to turn off re-enrollment in case a specific field (in this case, “close date”) changes. We have it set up so a task goes to someone anytime the deal close date changed in the last 1 day. Does anyone have any ideas to further limit the trigger criteria to eliminate duplicates but still allow re-enrollment?
Hi @AAdkins24,
You could create a “Last task create date” property and set a time stamp in your workflow right after the task is created. Further up in the workflow, you could check (in an if/then branch) whether that date property is known or not. If it’s known, you would send the record down a path where you’re not creating a task. If the date property isn’t known, you could create the task.
Alternatively, you could create an if/then branch which branches on activities/engagement. This branch would check whether there is already an activity with Activity type “Task” and a specific Title associated to the deal. If there is, you’d skip task creation. If there isn’t, you would proceed as before.
Let me know if you have any follow-up questions!
Thank you so much, Karsten! I will give this a try!
Hey there, I want to bump this thread because it’s an example of a common HubSpot frustration. For anyone landing here from Google, the problem is that workflows struggle to check for association properties’ values. This became problematic enough for me to build out a utility to fix it cleanly
It’s a single workflow action that automatically prevents duplicate tasks—no if/then branches or custom properties needed. You can see a 30-second demo of how it works at https://workflowheros.com/task-sentinel Hope it saves someone else the trouble.