All articles

Recurrent Tasks

Table 43. Availability - Legacy plans


All users (except for collaborators) on all account types can make tasks recurrent unless it's restricted by their access role.

When you make a task recurrent, Wrike automatically creates duplicates of that task according to your settings. You can set:

  • How often a task should be created.

  • The date that the recurrence should end by or how many tasks should be created in the sequence.

  • How many tasks should exist at a time.

How recurrent tasks work

The original task is the first task in the sequence. Recurrent tasks have the same status as the original task and their titles are based on the first task’s title. The recurrent task's start date 1 is added to its title.


Changes that you make to a task in the recurrence, e.g., edit the description or task status will not transfer to the next task in the recurrence automatically. If you want to update all the subsequent tasks, you need to edit the recurrence itself.

Upfront tasks: By choosing to create tasks upfront, you specify how many tasks you want to have in the workspace at a time until the recurrence ends. If you choose not to create any tasks upfront, Wrike creates recurrent tasks one by one.

Each next task in the recurrence sequence is created automatically, just before its start date.


If 15 consecutive tasks in the sequence aren't modified (i.e., the description isn't changed, no comments are added, etc.) the recurrence is paused and no new tasks are created unless you manually resume the recurrence.

If you need to edit a task recurrence, you don't need to find the original task. Just select any task that was created within the relevant recurrence and edit from it.


Can I make subitems recurrent together with the parent task?

When you make a task recurrent, its subitems aren't included in the recurrence.

What happens with recurrence when its author is deleted from the account?

If the user who created a recurrence sequence is removed from the account or downgraded to a collaborator, the recurrence is stopped (no new tasks are created in the sequence).