Task creation based on ticket status - how to avoid duplicate tasks

[CMarritt]

tiWe have a workflow based on a ticket pipeline and tasks are created based on which ticket status the ticket is moved to, but sometimes the ticket might move back to a status it's already been in, which triggers the tasks to be recreated even when they've been ticked off. 

Is there a way to stop this recreation of the tasks? I tried adding 'has never been x status' but that negated itself with the current status and went to 'none met'

[karstenkoehler · Accepted solution]

Hi @CMarritt,

If you do not want the task to be recreated, you would disable re-enrollment for this workflow: https://knowledge.hubspot.com/workflows/add-re-enrollment-triggers-to-a-workflow

Should there be other workflow actions that should re-run when a ticket moves back in status, then it's best / easiest to split the workflow in two. One workflow re-enrolls and takes care of actions that should be repeated. Another workflow has re-enrollment disabled, only runs once and create tasks, once.

Let me know if you have any follow-up questions!

[CMarritt]

Hi Karsten, 

Thanks for your reply, is there any other way to do this without turning off re-enrollment? We have 9 status' for this pipeline, this would be separating the current workflow into 9 individual WFs as we currently use if/thens depending on the ticket status 

[karstenkoehler]

Hi @CMarritt,

All alternatives that I can think of would involve even more additional work, unfortunately. Splitting these workflows is, as far as I can tell, the easiest and fastest solution.

Best regards!