Editing the Due Date of a Single Recurring Task Instance (Without Changing Future Ones)

Request: Please add the ability to change the due date for one instance of a recurring task without updating all future recurrences.

Why this matters
Recurring tasks are often used for annual, seasonal, or event-based workflows (events, campaigns, audits, programs, etc.). While the structure stays the same, dates don’t always.

Current behavior
Changing the due date on a recurring task updates every future recurrence.

The problem
This makes it hard to handle one-off changes, like:

  • This year’s event date shifts, but future years don’t

  • A single project needs to be postponed

  • One cycle changes without affecting long-term planning

The workaround today is duplicating tasks or rebuilding workflows — time-consuming and error-prone.

What would help
An option to:

  • Edit or postpone only the selected instance (or upcoming cycle)

  • Keep all future recurrences on their original schedule

This small change would add a lot of flexibility and make recurring tasks much easier to use for long-term planning.

1 Like

Welcome, @Sarah_Von_Hoene,

I think it actually already works exactly the way you want!

I just tested it to confirm what I had recalled and it operates like this:

Set a task recurring date for 3/1 repeating monthly on day 1 of the month.

Change that task’s due date to 3/2; it changes this recurrence’s due date, but doesn’t affect the repeat setup.

Mark this task complete.

A new task is generated with the date of 4/1, honoring the original repeating setup regardless of the current task’s due date change.

Thanks,

Larry

Larry,

Thank you for clarifying! This will be helpful for me and my coworkers.

1 Like