Multiple tasks are created
SOLVEHello everyone,
Has anyone else encountered the same issue, where multiple duplicate tasks are being created at the same time? If so, I’d appreciate any insights or solutions you’ve found.
Could someone advise me on how to prevent this from happening? We create these tasks for various customers, so a solution like "don't create if the task name already exists" wouldn't work in this case. I'm looking for an alternative approach that could help.
1 Accepted solution
Multiple tasks are created
SOLVE@EAsta before the task creation, and an and/or branch and add an activity filter, checking whether the record is associated to an activity with task name "Complete handover [...]" and task status is none of completed. In the left branch, nothing happens. If the criteria are not met, the task would be created.
| Karsten Köhler |
 | Did my post help answer your query? Help the community by marking it as a solution. |
Multiple tasks are created
SOLVEMultiple tasks are created
SOLVEHi @EAsta,
As a first step, you would have to find out how these tasks are created. It looks like there's a workflow behind this – which is likely configured incorrectly. Potentially, there are multiple workflows. There could also simply be faulty enrollment criteria which trigger too often.
To find the workflows, navigate to any record that has one of these tasks and filter the activity timeline by workflows: https://knowledge.hubspot.com/records/filter-activities-on-a-record-timeline
Now check all of the workflows that are listed.
And yes, before creating a task, you could add a and/or branch to check whether the record is already associated with an activity where the task title is X and the status is none of completed.
Once you share screenshots of the workflows, I can provide more in-depth instructions – but generally, that's how you would have to approach this.
Best regards!
| Karsten Köhler |
| Did my post help answer your query? Help the community by marking it as a solution. |
Multiple tasks are created
SOLVEThank you for your quick reply Karsten. So what we do (screenshot of the workflow is added below), is that we want to trigger a workflow (onboarding) when new customer is added to our environment. Therefore we use customer phase 'onboarding' as the trigger.
Multiple tasks are created
SOLVE@EAsta before the task creation, and an and/or branch and add an activity filter, checking whether the record is associated to an activity with task name "Complete handover [...]" and task status is none of completed. In the left branch, nothing happens. If the criteria are not met, the task would be created.
| Karsten Köhler |
| Did my post help answer your query? Help the community by marking it as a solution. |
