Tasks are locked into the ruleset that existed when they were created so if you make a change to routing rules and want existing tasks to follow that change you will need to cancel and recreate tasks in queue.
This article will show an example of recreating tasks that belong to a specific campaign, but the premise is the same even if the tasks don't share a campaign.
Step 1: Identify a task attribute shared by all tasks you're recreating
In this example, we'll be canceling tasks that belong to campaigns #115 and #118. The premise is the same if you need to use another task attribute such as created_at, type, or queue (although you will likely need substantially more conditional node splits).
Step 2: Set up a journey to cancel and recreate the tasks
- The journey should trigger on task.canceled with a property condition that targets the tasks your canceling. It should also have a property of canceled_by is [your email] to avoid a situation where someone else cancels a task that you don't want recreated.
- In this example, we'll use task.canceled where campaign_friendly_id Is One Of 115 or 118
- Set up conditional splits to identify the campaign
- Condition Type: Triggering Event
- Property values: properties.campaign_friendly_id = 115
- Repeat step 2 for any other campaigns or other identifying attributes.
- If you have multiple conditional nodes, connect the nodes so that if they evaluate to false, it moves the next conditional node.
- Connect the appropriate task recreation node. In this case, both campaigns are call tasks.
- Save the journey as live.
- In this example, we'll use task.canceled where campaign_friendly_id Is One Of 115 or 118
It is very important to save the journey as live before canceling the tasks.
Step 3: Cancel tasks
- Navigate to the tasks page and filter for the tasks you want to recreate
- Once the tasks are filtered, select all tasks and click Cancel
- Wait for the journey you set up earlier to recreate the tasks
It's a best practice to monitor the new tasks for a few minutes as they get created and assigned to ensure that the changes to task routing are acting the way you expect them to.