---
url: /reference/repeat-rules.md
description: >-
  How a recurring task picks its next date in each mode, what carries over, and
  when a series ends.
---

# Repeat rules

This page lists how a recurring task picks its next date in each mode, what each new task copies,
and when a series stops. To set a rule up, see
[Set up a recurring task](/guides/set-up-recurring-tasks).

## Repeat modes compared

A rule has one of two modes, chosen in **Mode** in the repeat editor:
[**Fixed schedule**](/guides/set-up-recurring-tasks#repeat-on-a-fixed-schedule) or
[**After completion**](/guides/set-up-recurring-tasks#repeat-after-completion). A new rule starts
in **After completion**, every 1 **Day**.

| | **Fixed schedule** | **After completion** |
|---|---|---|
| New task appears | on its date, at the **at** time, whether or not you completed the last one | at once, when you complete the current task |
| Next date counts from | the rule's own calendar | the current task's occurrence date or its due date, whichever is later |
| **at** (time of day) | used; 09:00 by default | hidden (see [Next date: After completion](#next-date-after-completion)) |
| **Ends** | used | shown while you set the rule up, but not saved: after **Save** it reads **Never** and the summary drops **· until …** or **· N times**; the series runs until you stop it |
| **Skip next** | works | shown, but gives an error |
| Summary line | **Every week on Fri at 09:00** | **Every week on Fri · after completion** |

Complete means moving the task to a status in the **Done** [stage](/concepts/statuses).

## Frequency: units and days

**Every** sets how many units pass between tasks; the unit's name turns plural (**Days**,
**Weeks**) when **Every** is more than 1.

| Unit | You also pick | Preselected from the due date (or today) | Summary example |
|---|---|---|---|
| **Day** | nothing | — | **Every 2 days at 09:00** |
| **Week** | one or more weekdays, in **on** | its weekday | **Every 2 weeks on Mon, Thu at 09:00** |
| **Month** | the day of the month, in **on day** (1–31), or **Last day of the month** | its day of the month | **Every month on day 1 at 09:00**, **Every month on the last day at 09:00** |
| **Year** | the month and the day, in **on** | its month and day | **Every year on Mar 5 at 09:00** |

Five weekdays Monday to Friday read **weekdays** in the summary, all seven read **every day**. In
a **Fixed schedule** series, "every 2 weeks" and "every 3 months" count from the week or the month
you first saved the rule in; later edits keep that cycle.

### Month-end days: 29, 30, 31

A monthly rule on day 29, 30 or 31 skips every month that doesn't have that day. A yearly rule on
February 29 creates a task only in leap years.

Example: **Every month on day 31**.

| Months | Task on the 31st |
|---|---|
| January, March, May, July, August, October, December | yes |
| February, April, June, September, November | none |

To get a task at the end of every month, use
[**Last day of the month**](#last-day-of-the-month).

### Last day of the month

Tick **Last day of the month** instead of typing a day: the **on day** field hides, and the
summary reads **Every month on the last day at 09:00**. Each task falls on that month's own last
day, February included. Clear the tick to go back to a day number; **on day** comes back set to the
day of the task's due date (or today's).

Example: **Every month on the last day**, set on September 14, 2026.

| Month | Task on |
|---|---|
| September 2026 | the 30th |
| October 2026 | the 31st |
| November 2026 | the 30th |
| February 2027 | the 28th |
| February 2028 | the 29th |

## First date of a series

The task you set the rule on becomes the series' first task. Its due date moves to the rule's first
date on or after today, or on or after the task's due date if that is later.

| You set the rule on… | Rule | The task's due date becomes |
|---|---|---|
| Friday, Oct 2, task due Oct 2 | **Every week on Fri** | Fri, Oct 2 |
| Wednesday, Sep 30, no due date | **Every month on day 1** | Oct 1 |
| Wednesday, Sep 30, task due Oct 20 | **Every month on day 1** | Nov 1 |

A rule set on the very day it names starts that day, even when its **at** time has passed.

## Next date: Fixed schedule

A **Fixed schedule** series follows its calendar. Each new task is created on its date at the
**at** time and is due that day. The next date doesn't depend on what happens to the current task.

Example: **Every month on day 1 at 09:00**, set on September 30. The first task is due October 1.
On November 1 at 09:00 the next task appears, even if October's task is still open.

A series creates at most one task per day. Each series runs in the time zone of the device it was
set up on, not the **Zone** under **Time zone** in your
[notification settings](/guides/set-up-notifications#settings-page-one-per-workspace).

## Next date: After completion

An **After completion** series creates the next task when you complete the current one. The next
date is the rule's first date after the current task's **occurrence date** (the date the series
gave it) or its due date, whichever is later. The day you complete the task doesn't count.

Example: two series whose current task has occurrence date and due date Friday, October 2 —
watering the plants, **Every 3 days · after completion**, and a review, **Every week on Fri · after
completion**.

| You… | Every 3 days | Every week on Fri |
|---|---|---|
| complete it on October 1 or October 3 | Monday, October 5 | Friday, October 9 |
| move its due date to Monday, October 12, then complete it | Thursday, October 15 | Friday, October 16 |
| complete it on October 14, without moving the due date | Monday, October 5: overdue at once | Friday, October 9: overdue at once |

Example: a haircut, **Every month on day 15 · after completion**, due October 15. Completed early
or late, the next task is due November 15; with its due date moved to November 20 first, it is due
December 15.

::: tip Late? Move the due date first
If you complete a task long after its due date, move the due date to today before you complete it.
The next task then counts from today's date instead of the old one.
:::

::: warning Bulk completion doesn't continue the series
Completing tasks several at a time from the bulk bar doesn't continue the series. Complete a
recurring task on its own; see [Edit tasks in bulk](/guides/edit-tasks-in-bulk).
:::

### Time of day in After completion

**After completion** has no **at** field. If the task has a due time, each new task is due at the
rule's **at** time: 09:00, unless you set another time before switching to **After completion**.
New tasks of an all-day task stay all-day.

Example: a review, **Every week on Fri · after completion**, due Friday, October 2 at 15:00. The
next task is due Friday, October 9 at 09:00.

## Ends: when a series stops

**Ends** applies to **Fixed schedule** only. In **After completion** it isn't saved.

| Option | What it does | Default |
|---|---|---|
| **Never** | The series runs until you stop it. | — |
| **On date** | The series stops before the date you pick: its last task is on the day before at the latest. To include a date, pick the day after it. In a time zone ahead of UTC, an **at** time up to the zone's offset (such as 09:00 in UTC+10) still gets a task on the date you pick. The summary adds **· until** and the date. | one month from today |
| **After N occurrences** | The series stops after N tasks. The task you set the rule on counts as the first; skipped dates don't count. The summary adds **· N times**. | 10 |

When a series ends, the tasks it already created stay.

## Carry over: what a new task copies

Each new task is a copy of the series' template: a snapshot of the task you set the rule on, taken
once, when you save the rule. **Carry over** picks the fields it copies; **All fields** is the
default.

| Field | Copied |
|---|---|
| Title | always |
| [Start date and due date](/guides/create-and-edit-tasks) | always, moved to the new date; a start–due range keeps its length |
| [**Description**](/guides/write-a-task-description) | unless you clear it in **Carry over** |
| [**Priority**](/guides/create-and-edit-tasks) | unless you clear it |
| [**Assignee**](/guides/assign-and-watch-tasks) | unless you clear it |
| [**Tags**](/guides/tag-tasks) | unless you clear it |
| [**Time estimate**](/guides/track-time) | unless you clear it |
| [**Subtasks**](/guides/break-down-with-subtasks) | unless you clear it |
| [Comments](/guides/comment-and-mention) | never |
| [Watchers](/guides/assign-and-watch-tasks) | never |
| [Story points](/guides/estimate-with-scrum-poker) | never |
| [Relations](/guides/link-related-tasks) | never |
| [Tracked time](/guides/track-time) | never |

With some fields cleared, **Carry over** reads, for example, **4 of 6 fields**; with all six
cleared, **Title only**. See [Task fields](/reference/task-fields) for what each field holds.

### Status of a new task

A new task's status depends on the mode. To change the list's statuses, see
[Change statuses](/guides/set-up-a-list#change-statuses).

| Mode | A new task starts in |
|---|---|
| **Fixed schedule** | the status new tasks in the list start in |
| **After completion** | the status the task had when you set the rule; if that status was in the **Done** stage, the status new tasks in the list start in |

## Series controls

These open from the rule next to **Repeats** in any task of the series, or from a series' **…**
menu in **Workspace settings** → **Recurring Jobs** (see
[Pause, skip or stop a series](/guides/set-up-recurring-tasks#pause-skip-or-stop-a-series)).

| Control | What it does | Modes |
|---|---|---|
| **Pause** | Stops new tasks. The field reads **Paused ·** and the rule. | both |
| **Resume** | Starts a paused series again. In **Fixed schedule**, if a date passed while it was paused, one task appears at once, dated the day you resume; after that the series follows its calendar. | both |
| **Skip next** | Skips the next date; the series goes on from the date after it. | **Fixed schedule** only; on **After completion** it gives an error |
| **Don't repeat** (in the task) or **Cancel** (in **Recurring Jobs**) | Deletes the series: no new tasks. To repeat again, set a new rule. | both |

::: danger Don't repeat and Cancel can't be undone
The rule can't be restored after **Don't repeat** or **Cancel**. Tasks already created stay.
:::

## Edits to a saved series

* **Mode is locked.** A saved series keeps its mode. To switch, click **Don't repeat** and set the
  rule again in the other mode.
* **These can be changed**, and the change applies to the tasks created after it:
  * **Frequency**;
  * **Ends** (**Fixed schedule** only);
  * **Carry over**.
* **Task content is fixed at setup.** Later edits to the task you set the rule on, or to any task
  of the series, don't change the tasks that follow.
* **[Turning Repeats off in the list](/guides/set-up-a-list#turn-features-on-or-off)** hides the
  **Repeats** field, but the list's series keep creating tasks. Stop them in **Workspace
  settings** → **Recurring Jobs**.

## Permissions for recurring tasks

The permissions sit in the **Recurring jobs** block of a
[permission set](/reference/permissions-and-access); the default **Worker** set has all four.

| Action | Permission in **Recurring jobs** | Also needs |
|---|---|---|
| See **Workspace settings** → **Recurring Jobs** | **Read** | — |
| Make a task repeat | **Create** | [**Edit** access](/concepts/sharing) to the list |
| Edit a rule, **Pause**, **Resume**, **Skip next** | **Update** | **Edit** access to the list |
| **Don't repeat**, **Cancel** | **Delete** and **Update** | **Edit** access to the list |

Without **Delete** or **Update**, **Don't repeat** and **Cancel** are hidden.