Flow: recurring tasks

SENSEVER

The official Sensever channel: guides and API documentation for Chat, Requests, Flow, Studio, bots and messaging channels.

9 хв читання

Flow: recurring tasks

Some tasks come back again and again: a weekly stand-up, a report on the last Friday of the month, watering the plants three days after the last time. In Flow, you don't have to create such a task from scratch each time: set up recurrence once, and the next task appears on its own — with the same title, assignee, and fields, but a new due date. This article explains how to set up recurrence, when new tasks are created, and what is copied into them.

Two recurrence modes

Mode

When the next task appears

Example

"On schedule"

On its calendar date, even if the previous one is not closed yet

"Every Mon and Thu", "Monthly: 2nd Tue", "Every weekday"

"After completion"

Only when the current task is closed; the new due date is the set interval after the day it was closed

"3 days after completion"

"On schedule" suits regular meetings and reports tied to the calendar. "After completion" suits things where the gap between occurrences matters: if a task is closed late, the next one shifts with it.

How to set up recurrence

Recurrence is set up in the object card. In the fields block, right below the object's date (usually "Deadline"), there is a "Repeat" button. It opens the "Repeat task" window.

  1. Choose a mode: "On schedule" or "After completion".

  2. Choose the "Frequency" and "Interval" (in "After completion" mode the field is called "After how long").

  3. For weeks and months, specify the days (see below).

  4. Choose when the series "Ends".

  5. Check the plain-language description and the "Next dates" at the bottom of the window.

  6. Click "Save". Flow reports "Repeat set up".

Recurrence works for objects of any type, not just tasks. You need permission to edit the object, and the type must have a published schema; an archived object cannot recur.

Frequency and interval

Frequency

Interval

Extra

"Daily"

every Nth day

—

"Every weekday"

none (Monday to Friday)

only in "On schedule" mode

"Weekly"

every Nth week

"Days of week" — one or more buttons Mon…Sun

"Monthly"

every Nth month

"By date" or "By weekday"

"Yearly"

every Nth year

month and day — the same as the task's due date

The interval is from 1 to 365.

Weeks. Select the days you need with the buttons in the "Days of week" row. If you select none, the task recurs on the weekday of its due date. "Every two weeks" counts from the week of the first task's due date: that week, then every other week. Weeks start on Monday.

Months. Two options:

  • "By date" — "Day of month": 1–31, "last day", or "as the task due date". If a month has no such day, the task lands on the last day of the month: "31st" becomes April 30 in April and February 28 or 29 in February. No month is skipped.

  • "By weekday" — the week of the month ("1st week" … "4th week", "last week") and the weekday: for example, "2nd Tuesday" or "last Friday".

Years. The task recurs on the same month and day as its due date. February 29 becomes February 28 in a non-leap year.

In "After completion" mode, you don't choose weekdays or dates: the next due date is the closing day plus an interval in days, weeks, months, or years.

Series end

Option

Meaning

"Never"

Tasks keep being created until recurrence is stopped

"Until a date"

The last task falls no later than the "End date" (inclusive). The date cannot be earlier than the first task

"After N times"

"How many times, including this task" — from 2 to 1000. The current task counts as the first

Description and next dates

While you change the settings, the window describes the rule in words — for example, "Every Mon and Thu, until 31.12.2026", "Every month: 2nd Tue", "3 days after completion, 10 times". Below that:

  • in "On schedule" mode — "Next dates": the next five due dates, calculated by the server;

  • in "After completion" mode — "If completed today": the due date of the next task if you close the current one today.

If the rule produces no dates at all (for example, the series ends before the first recurrence), you see an error instead of dates.

Which date recurrence counts from

The starting point is the due date of the task you set recurrence on. If there is no due date, it is today. This task becomes the first in the series, and the following dates come strictly after it.

Which field counts as the due date:

  • the field with the key due_date ("Deadline"), if the type has one;

  • otherwise, the first "Date" or "Date and time" field (other than the start date).

A task without a due date field can recur too: then the dates only determine when the new task appears.

Dates are calculated in your browser's time zone at the moment of setup. A "Date and time" field keeps its time: if the task is due Monday at 10:00, the following tasks are also due at 10:00 in that time zone, even after the switch to daylight saving time.

When the next task appears

On schedule. The new task is created in advance — at midnight before its date (in the series' time zone), whether or not the previous ones are closed. That is why a daily series usually has two open tasks: today's and tomorrow's.

After completion. The new task is created as soon as the last task in the series moves to a status of the "completed" kind. Its due date is the closing day plus the interval.

  • Moving to a "canceled" status does not continue the series: the task is no longer needed. If you still need recurrence, set it up again.

  • Only the last task continues the series. Closing an older task in the series, or closing an already closed task again, does not create a second copy.

If Flow could not create tasks for a while (for example, after a service outage), it does not create a batch of overdue tasks for every missed date. It creates one task — for the date closest to today — and the missed dates count toward the series' number of recurrences.

One series date means one task: even with failures and retries, Flow never creates two copies for the same date.

What is copied into the new task

The new task is copied from the last task in the series. If you changed the description, priority, or assignee in the last task, the following tasks get the new values.

Copied:

  • title and assignee;

  • fields: strings, text, numbers, money, "Yes/no", lists and multi-select lists (for example, priority), members (for example, watchers), tags, JSON;

  • the checklist — all items, but without check marks;

  • the due date — the date of the new recurrence; the start date (start_date, if any) shifts by the same number of days as the due date;

  • "many to one" relations on the task's side — project, milestone, parent task — if the related object is not archived.

Not copied:

  • other date fields — the new task did not have them yet;

  • read-only fields and the closing outcome;

  • blockers and other "many to many" relations;

  • the discussion, files, history, and time entries.

The new task is created in the process's initial status, using the current version of the type's schema: fields no longer in the schema are skipped. Tasks are created on behalf of the person who set up recurrence: the new task's history says it was created by an automation on their behalf.

If the last task is archived, the last non-archived task in the series becomes the template. If all of them are archived, the series ends.

The series in the card

You can see and configure the series from any of its tasks. A task with active recurrence shows a series line instead of the "Repeat" button:

  • the recurrence icon and the rule in words;

  • "Next: …" — the date of the next task, or, in "After completion" mode while the current task is open, "Next one — after completion";

  • the "Edit" and "Stop repeating" buttons.

Edit opens the same window with the current rule. The new rule applies going forward from the last task in the series: tasks already created are not changed or deleted, and the recurrence count continues.

Stop repeating stops new tasks from being created (Flow reports "Repeat stopped"). Tasks already created stay. The task then shows the "Repeat" button again: a new setup continues the series from its last task, and the recurrence count starts over.

When a series reaches its end date or the required number of recurrences, the card says "The repeat series has ended".

Icon in lists

On the board and in the table, tasks with active recurrence have a recurrence icon next to the title with the tooltip "Recurring task". Stopped and ended series have no icon.

If a task was not created

Sometimes Flow cannot create the next task: the person who set up recurrence no longer has permission to create objects of this type, was removed from the workspace, the type got a new required field with no value, or the type was archived. Such an error won't fix itself, so instead of retrying every period, Flow stops the series. The card shows the warning "Repeat stopped: the task could not be created." with the reason.

What to do: fix the cause (restore permissions, fill in the required field in the last task, or make it optional) and click "Repeat" again.

Errors in the rule window are shown below the settings. Common ones:

Message

What to fix

"The end date is earlier than the first task"

Choose a later end date

"Number of times: from 2 to 1000 (including the first task)"

Fix "How many times"

"Interval must be a whole number from 1 to 365"

Fix the interval

"The rule produces no dates"

The rule never fires — change the days or the end

"Publish the type schema"

The type has no published schema — publish it in the type settings

Tips

  • Set up recurrence on a task that already has its assignee, checklist, and description filled in: all of it carries over to the following tasks.

  • There are no schedule exceptions ("skip January 1"). In "On schedule" mode, you can archive an unneeded task in the series — the following ones will still appear. This doesn't work in "After completion" mode: the next task appears only after the current one is closed, so it's better to close the unneeded task.

  • To change the content of all following tasks, change the last task in the series.

What's next

Коментарі

Автори