Issue Summary

• Due to the limitation of 150 tasks for each branch as mentioned here, in order to narrow down the tasks to be iterated the "Due date is coming up in" and "Due date has passed" criteria are used in the task branches.

• However, we have observed unusual behavior when using those criteria.
  • When we attempt to iterate tasks with due dates set for tomorrow and configure the "Due date is coming up in" criteria to 1 (the minimum allowable value, as it cannot be set to 0), the tasks scheduled for tomorrow are not being iterated.
    • Instead, tasks with due dates set for 2 days later are being iterated.
  • Similarly, when we attempt to iterate tasks with due dates set for yesterday and configure the "Due date has passed" criteria to 1 the tasks scheduled for yesterday are not being iterated.
    • Instead, tasks with due dates set for 2 days before are being iterated.

Steps to Reproduce

1. Create an automation rule in Confluence Cloud.
2. Insert a Task branch.
3. Add a "Due date" criteria.
4. Select either the "Due date is coming up in" or "Due date has passed" criteria.
5. Set the days field to 1.

Expected Results

• We expect the tasks with the due date tomorrow to be iterated when the "Due date is coming up in" criteria is set to 1.
• Similarly, we expect the tasks with the due date yesterday to be iterated when the "Due date has passed" criteria is set to 1.

Actual Results

• Instead, tasks with due dates set for 2 days later are being iterated.
• Instead, tasks with due dates set for 2 days before are being iterated.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available