When a task list is set to trigger based on a specific anchor event, and we make a change in Bob, but the trigger time has already passed, Bob can act in different ways:
·Making a change before the anchor event - If we make a change 5 days before the anchor event and have tasks that are set to trigger 30 or 20 days before the anchor event, Bob will trigger them as soon as possible (might take up to 6 hours after making the change in the system). In sum, all the tasks are triggered, just not in the correct time frame as the change wasn't made in advance.
·Making a change after the anchor event - This is where the 7-day rule is put in place. We have 3 situations.
o If the change is made up to 7 days after the anchor event, all tasks that are set to trigger after the anchor date will trigger. The tasks set to trigger before the anchor event won't.
o If the change is made on the anchor event, all tasks set to trigger before and on the anchor event will trigger on that day.
o If we make a change 8 days after the trigger timing of each task, these won’t trigger.(It's been too long since the trigger timing)
- This is where we'll need to manually trigger the task list if we really want it to trigger for that employee.
- Note that any tasks that were already triggered will also be triggered again.
- To account for this, you can duplicate the task list without the tasks that were already triggered.
Adding below a visual representation to the Task List behaviour:
