# Workflow generating duplicate tasks with re-enrollment

**URL:** <https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026>\
**Category:** Lists, Lead Scoring & Workflows\
**Tags:** object\
**Created:** [June 14, 2022, 5:57pm UTC](https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026 "2022-06-14T17:57:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AAdkins24](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@AAdkins24](https://community.hubspot.com/u/AAdkins24)\
**Post date:** [June 14, 2022, 5:57pm UTC](https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026/1 "2022-06-14T17:57:57Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![karstenkoehler](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/karstenkoehler/32/68554_2.png) [@karstenkoehler](https://community.hubspot.com/u/karstenkoehler)\
**Post date:** [June 15, 2022, 4:27am UTC](https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026/2 "2022-06-15T04:27:39Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![AAdkins24](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@AAdkins24](https://community.hubspot.com/u/AAdkins24)\
**Post date:** [July 5, 2022, 9:16pm UTC](https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026/3 "2022-07-05T21:16:27Z")

</div>

Thank you so much, Karsten! I will give this a try!

---

<div class="post-metadata">

**Author:** ![HubBubDotXYZ](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hubbubdotxyz/32/70044_2.png) [@HubBubDotXYZ](https://community.hubspot.com/u/HubBubDotXYZ)\
**Post date:** [October 17, 2025, 5:11pm UTC](https://community.hubspot.com/t/workflow-generating-duplicate-tasks-with-re-enrollment/59026/4 "2025-10-17T17:11:36Z")

</div>

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](https://workflowheros.com/task-sentinel) Hope it saves someone else the trouble.