Hule Docs

Appearance

Recurring tasks ​

A recurring task (also called a recurring job) is a task template that automatically spawns new task instances on a schedule. Use them for routines: daily standup notes, weekly status reports, monthly invoicing, quarterly reviews.

Creating a recurring task ​

  1. Open the list where you want tasks to appear.
  2. Click the dropdown next to + Add task and select + New recurring task.
  3. Fill in the template (title, description, priority, tags — the content that every occurrence will copy).
  4. Configure the schedule.

Schedule ​

Frequency ​

FrequencyWhat it means
DayEvery N day(s) — e.g. every 2 days
WeekOn specific day(s) of the week, every N week(s) — e.g. every Monday and Wednesday, every 2 weeks
MonthOn a specific day of the month (1–31), every N month(s) — e.g. on the 15th, every 3 months
YearOn a specific month and day, every N year(s) — e.g. January 1st, every year

Each frequency also requires a time of day (HH:MM) and a timezone (IANA format, e.g. Europe/Moscow or America/New_York). The time of day determines when the task appears as "due on" that day.

End condition ​

ConditionBehaviour
NeverThe series runs forever
On dateThe series stops after a specific calendar date
After N occurrencesThe series stops after N tasks have been spawned

If no end condition is set, the series runs until you pause or delete it.

Spawn status ​

By default, each spawned task is created in the first open status of the target list. You can override this by choosing a specific status (e.g. "To Do" or "In Progress") when creating the recurring task. All future occurrences will use that status.

How spawning works ​

A background job runs every minute and checks for recurring tasks that are due. When a task is due:

  1. A new task is created from the template into the target list.
  2. The new task is tagged with a seriesId linking it back to the recurring job.
  3. The recurring job's schedule is advanced to the next due time.

If multiple occurrences were missed (e.g. you were away for a week), each one is spawned in sequence until the scheduler catches up.

Editing occurrences ​

After a task instance is spawned from a recurring series, you can edit it like any normal task. The question is: does your edit affect just this one task, or the entire series?

Open the task instance and click Edit series — you'll see three modes:

This occurrence only ​

Changes apply only to this specific task instance. The date of this occurrence is added to the series' skip list so that when the series repeats, a new task is created as usual.

Use this when: the task for this week needs different details, but next week's should be normal.

This and following occurrences ​

Creates a split in the series. The old series is ended at the day before this occurrence, and a new series is created with your changes going forward. Past instances keep their original data.

Use this when: the scope of a recurring meeting changes starting today, but past meetings should stay as recorded.

All occurrences (past and future) ​

Applies your changes to the task template, then bulk-updates all past instances from the same series with the same changes (title, description, priority, tags). Dates and statuses of past instances are preserved.

Use this when: you renamed a recurring meeting or updated its default description.

Skipping occurrences ​

Sometimes you don't want to edit — you just want to skip one or more upcoming occurrences.

Skip next occurrence: Open the recurring task settings and click Skip next. The next due date is skipped and the schedule advances.

Skip until a date: Open the recurring task settings and click Skip until — choose a date. All occurrences between now and that date are skipped. Clear the skip date to resume normally.

Pausing and resuming ​

Toggle the Active switch on the recurring task settings to pause or resume the entire series. While paused, no new instances are spawned.

Deleting a recurring task ​

Deleting a recurring task removes the series definition — future instances will not be spawned. Existing task instances that were already spawned remain in your list as regular tasks (they keep their seriesId link but it's purely informational).