Recurring Tasks

Recurring Tasks are for things you need to do again, not things you would like to remember again.

You might create one for a weekly workout, a monthly credit-card payment, or washing the football kit every Saturday. Harmonise creates a separate Task for each Due Date, so completing this Saturday’s kit does not complete every future Saturday as well.

A recurring Task can repeat in two ways:

• It can follow its own Due Date.
• It can follow a recurring Event, such as preparing notes for every weekly meeting.

This guide focuses first on Tasks that repeat by themselves. Tasks that follow Events are covered near the end.

When should a Task repeat?

Use repeat when the same kind of Task returns on a regular pattern.

Task	Useful repeat pattern
Wash the football kit	Every Saturday
Take medicine	Every day
Pay the credit-card bill	Every month
Review the household budget	First day of every month
Renew the parking permit	Every year

A recurring Task needs a Due Date

A standalone recurring Task repeats from its Due Date. There is no separate choice for what controls the series.

The Due Date can be:

• a date, such as every Friday; or
• a date and time, such as every Friday at 5:00 PM in the Task’s timezone.

For example:

Pay the credit-card bill

• Due Date and Time: 25 July at 10:00 PM
• Repeat: Every month
• Estimated duration: 30 minutes

The next Task is due on 25 August at 10:00 PM. It begins without a Scheduled Date or Scheduled Date and Time, so you can decide when to work on that particular bill.

A Task without a Due Date cannot repeat. If you remove the Due Date from a recurring Task, remove Repeat for the same Task range as part of that change.

Note: A Scheduled Date, with or without a time, is when you plan to work on one Task. It does not create future Tasks, control the repeat pattern, become a series default, or copy to later Tasks.

What stays consistent between Tasks?

Each new Task uses the usual details for the recurring series, including its title, description, calendar, deadline reminders, subtask definitions, estimated duration, and Due Date recurrence.

Each new Task starts with no planned day, no scheduled start or end, and no scheduled-start reminders. Estimated duration can still be useful before you choose a time: it tells you how long the work may take without putting it on your calendar.

Completion, reopening, status, taken-by state, sort order, subtask completion, Scheduled Date, Scheduled Date and Time, and scheduled-start reminders belong to one Task occurrence. A scheduled start and its scheduled-start reminders are not copied to later Tasks.

A standalone recurring Task series keeps the timezone established when the series is created. This keeps an exact Due Date and Time, such as “Monday at 7:00 AM,” attached to one stored timezone across the series. Changing your profile or device timezone does not rewrite it. Event-linked recurring Tasks adopt the Event timezone during link or relink operations; see Tasks linked to Events.

Create a recurring Task

On mobile

1. Open the Create menu and choose Task.
2. Enter the Task title.
3. Choose an eligible writable calendar.
4. Add a Due Date. Turn on the time only when the Task has an exact Due Date and Time.
5. Open Add details when needed.
6. Under Repeat, choose how often the Task should return.
7. Choose when the series should end.
8. Add deadline reminders, subtasks, estimated duration, or a description when they help.
9. Add a Scheduled Date, and a time when useful, only when you want to plan this first Task.
10. Choose Create.

On web

1. Choose Create, then choose Task.
2. Enter the Task title.
3. Choose an eligible writable calendar.
4. Add a Due Date. Include a time only when the Task has an exact Due Date and Time.
5. Choose the repeat pattern and, when needed, its ending.
6. Add estimated duration, deadline reminders, subtasks, or notes.
7. Assign a Scheduled Date, and a time when useful, only when you want to plan this particular Task.
8. Choose Create task.

The mobile editor currently gives more room for custom repeat choices. Web supports the core daily, weekly, monthly, and yearly controls, but some detailed controls may be presented more simply.

Choose how often it repeats

Harmonise supports daily, weekly, monthly, and yearly patterns.

Common examples include:

• Every day
• Every week on Monday
• Every third Monday of the month
• Every 25th of the month
• Every year on 25 December
• Custom

You can also choose when the series ends:

• Never - continues until you stop it.
• On date - stops after a chosen date.
• After - stops after a chosen number of Tasks.

The first Due Date must fit the repeat pattern. When you change a pattern from one Task onward, Harmonise asks for a valid first Due Date instead of guessing one.

Complete or reopen one particular Task

Completing a recurring Task affects only the particular Task you selected.

If you complete Wash the football kit this Saturday:

• This Saturday’s Task becomes complete.
• Next Saturday’s Task remains open.
• The series continues.

The same is true when reopening a Task. Reopening one completed Task does not reopen other completed Tasks in the series.

Subtask completion belongs to one Task occurrence. In the current mobile and web Task flows, completing the final unfinished subtask can also complete that occurrence’s parent Task, and reopening a subtask can reopen a completed parent. Harmonise coordinates the parent status separately from the individual subtask change. Completing or reopening a subtask in one occurrence does not affect another recurring occurrence. Completing the parent Task may also mark its subtasks complete where the current platform flow supports it. Completing Add detergent this week does not complete the corresponding subtask in a future occurrence. Newly generated Task occurrences receive the subtask definitions in an incomplete state. Use the parent Task completion control when you want to complete or reopen the whole Task directly.

Choose which Tasks a change should affect

When you edit or delete a recurring Task, Harmonise may ask which Tasks should be affected. The choice depends on what you are changing. The exact Task scopes are This task, This and future tasks, and Entire series.

This task

Choose This task when the change is an exception.

Examples:

• Schedule this Saturday’s Task for Friday.
• Change the title for this particular Task.
• Change this Task’s Due Date without changing the repeat pattern.
• Add a special subtask for this week.
• Delete this particular Task because it is not needed this time.

The rest of the series continues normally. Changing a Scheduled Date, Scheduled Date and Time, scheduled-start reminders, completion, status, taken-by state, sort order, or a subtask’s completion always applies only to this Task.

If you remove a timed Scheduled Date and Time, its scheduled-start reminders are removed too.

A Scheduled Date or Scheduled Date and Time may be before, at, or after the Task’s Due Date. Harmonise may show a warning when planned work is later than the deadline, but the state remains valid and saving is not blocked.

This and future tasks

Choose This and future tasks when something changes from now onward. Harmonise keeps earlier Tasks in the original series and starts a successor series at the Task you selected.

Examples:

• Change the title for this and future Tasks.
• Change the estimated duration for future Tasks.
• Replace the subtask definitions for future Tasks.
• Change a weekly Task to repeat daily from this Task onward.
• Change the calendar from this Task onward.
• Stop the Task from this point forward.

The selected Task and future Tasks use the new setup. Its Scheduled Date or Scheduled Date and Time and scheduled-start reminders do not carry into the successor series.

When an edit includes a schedule placement as well as a wider change, the schedule-related part remains limited to This task. Estimated duration is separate and may use a broader Task scope where supported.

Entire series

Choose Entire series when the change belongs to the recurring Task as a whole.

Examples:

• Rename every Task in the series.
• Change the usual deadline reminder.
• Replace the standard subtask definitions.
• Change the repeat pattern, ending, Due Date recurrence, or calendar.

Completed and historical Tasks are preserved when recurrence details change. A series change does not automatically change a Task’s Scheduled Date or Scheduled Date and Time, scheduled-start reminders, completion, status, or other one-Task exceptions.

Schedule placement remains occurrence-only

Scheduled Date and Scheduled Date and Time belong to one Task occurrence. They do not control recurrence, become a recurring-series default, or copy to newly generated Tasks. Scheduled-start reminders follow the same occurrence-only rule.

Estimated duration is different. It describes the work and may use This and future tasks or Entire series where the edit supports those scopes.

A timed Task schedule uses a positive whole-minute duration and cannot be longer than 24 hours. If the schedule is later than the Due Date, Harmonise may show scheduled after deadline or may finish after deadline. The warning is cautionary; it does not make the Task invalid or block saving.

Change the repeat pattern

A repeat pattern describes the series, not just one particular Task.

You cannot change “weekly” to “daily” for only one Task and still call it the same repeat pattern. When changing the rule, choose either:

• This and future tasks to keep the past unchanged and use the new pattern from now on; or
• Entire series to update the whole recurring Task.

For example, a weekly Task due every Monday can become due every Tuesday and Thursday from this week onward. Earlier Mondays remain part of the old history; future Tasks follow the new pattern.

Remove recurrence

Removing recurrence is different from deleting Tasks. In the repeat editor, set the Task to Does not repeat. The current mobile and web editors support this for standalone recurring Tasks; a linked Event controls its own recurrence and does not use a separate Task repeat rule.

Remove recurrence from this and future tasks

Choose This and future tasks when the recurring series should end before the selected Task.

• Earlier Tasks remain in the earlier recurring series.
• The selected Task remains as a standalone, non-recurring Task unless a separate delete action removes it.
• No additional future Tasks are generated from that point.
• The selected Task keeps its occurrence-owned Scheduled Date or Scheduled Date and Time.
• The existing series attachment collection transfers to the selected surviving standalone Task rather than being copied to every resulting Task.

Remove recurrence from the entire series

Choose Entire series when the recurring rule should be removed for the whole series.

• The rule is removed and no new Tasks are generated.
• Required existing Task history is preserved as standalone Tasks according to the current recurrence contract.
• The selected surviving Task receives the applicable series attachments.

If a recurrence-removal scope is not offered for the Task you opened, save the supported changes separately or use the available scope. A linked Event, a read-only calendar, a synchronization barrier, or another Task relationship can limit which changes are currently safe.

Delete recurring Tasks carefully

Deleting Tasks is not the same as removing recurrence.

Delete this task

Only the selected Task is removed or excluded. Other Tasks in the recurring series continue.

Deleting one occurrence does not remove the recurring series attachment collection.

Delete this and future tasks

The selected Task and later Tasks in the affected recurring range are removed. Earlier Tasks remain in the earlier series. The selected Task does not automatically remain as a standalone Task.

The earlier source series remains the owner of its existing attachments; no attachment collection is copied to the deleted future range.

Delete the entire series

The recurring Task series is removed. Tasks that still belong to the series are removed with it, and its series attachment collection is deleted. A detached one-off Task can remain as a standalone Task under the current deletion lifecycle.

This is a deletion action, not a way to stop future generation while keeping the recurring Task history. Use Remove recurrence when you want to preserve the existing Tasks.

The current mobile and web deletion dialogs expose the three Task scopes, although the wording of a delete button may vary slightly. Choose the scope shown by the platform rather than assuming that a broad deletion leaves the selected Task standalone.

Attachments across a Task series

Recurring Task attachments belong to the recurring Task series. Every occurrence shares the same attachment collection; individual occurrences do not have separate collections.

Completing, reopening, moving, editing, or deleting only one occurrence preserves the series attachments. Deleting the complete series removes the series attachment collection. A file becomes available after it finishes processing successfully, and file uploads or updates require an internet connection.

A normal This and future tasks split leaves existing attachments on the earlier source series. The new future series starts without copied attachments.

When This and future tasks removes recurrence, the earlier series ends before the selected Task and its existing attachment collection transfers to the selected surviving standalone Task. Removing recurrence from the Entire series follows the same selected-Task transfer behavior.

When an Event-linked recurring Task is unlinked and becomes standalone, applicable series attachments are retained by the selected surviving standalone Task rather than copied to every resulting Task. Converting a standalone Task into a recurring Task keeps its existing attachment collection with the new recurring series.

Tasks that repeat with Events

Some Tasks should follow a recurring Event instead of using their own Task repeat rule.

Examples include:

• Prepare an agenda for every weekly team meeting.
• Bring slides to every recurring class.
• Take attendance for every lesson.

For an Event-linked Task, the Event supplies the effective deadline. A timed Event supplies its start as the Task’s effective Due Date and Time. A one-day all-day Event supplies its local Event date, and a multi-day all-day Event its first local Event date, as the Task’s effective Due Date. The Task’s Scheduled Date or Scheduled Date and Time tells you when you plan to do the work.

The Task may also have reminders, subtasks, attachments, estimated duration, notes or a description, and its own completion state. It does not have an independent Due Date or Due Date and Time, calendar, or Task repeat rule while it is linked to the Event. Its timezone is aligned with the Event during link or relink operations; see Tasks linked to Events.

When the linked Event moves, the Task’s Event-controlled deadline moves with it and eligible deadline reminders are recalculated. The Task’s Scheduled Date or Scheduled Date and Time does not move automatically, and scheduled-start reminders remain tied to that unchanged timed schedule. If planned work is now later than the Event-controlled deadline, the state remains valid. Harmonise may show a non-blocking warning, but saving is not blocked.

When adding a Task to a recurring Event, Harmonise can ask:

This event only

Choose This event only to add the Task only to the selected Event.

• Earlier Events do not receive the Task.
• Later Events do not receive the Task.
• The Task is linked to that Event but does not repeat with the Event series.

This and future events

Choose This and future events to add the Task to the selected Event and every eligible later Event in the series.

• Earlier Events do not receive the Task.
• The Task repeats by following the recurring Event.
• The Task does not have its own Task repeat rule.

Entire Event series

Choose Entire series to add the Task to every eligible Event in the series.

• Eligible earlier Events receive the Task.
• The selected Event receives the Task.
• Eligible future Events receive the Task.
• Deleted, excluded, or otherwise nonexistent Event occurrences do not receive the Task.
• The Task repeats by following the recurring Event.
• The Task does not have its own Task repeat rule.

These Event attachment choices are different from the ordinary Task scopes This task, This and future tasks, and Entire series.

If Event recurrence is explicitly removed, linked Tasks in the affected Event range are deleted. They do not become standalone recurring Tasks. Unlink a Task first when you want to preserve it. See Recurring Events for the Event recurrence rules and Tasks linked to Events for the complete workflow.

Offline and synchronization behavior

Harmonise can save some eligible core Task creates, edits, completions, reopenings, and deletions locally and synchronize them later when the relevant local Task write path is active.

Not every recurring change works offline. Eligibility can depend on the platform, local Task persistence, the calendar, the Task scope, recurrence identity, server-owned side effects, or a synchronization conflict or repair state.

Files and some subtask, Event-link, recurring-series, provider-owned, or other server-owned operations still require a connection. See Sync and offline use.

Common problems

I cannot turn on Repeat

A standalone Task needs a Due Date before it can repeat. Add a date-only Due Date or an exact Due Date and Time, then choose the repeat pattern.

For an Event-linked Task, the Event controls the deadline and recurrence. The Task does not use its own Task repeat rule.

I changed one Task, but future Tasks did not change

You probably chose This task. Edit the Task again and choose This and future tasks or Entire series, depending on how much of the series should change.

I changed future Tasks, but earlier Tasks stayed the same

That is expected when you choose This and future tasks. Earlier Tasks remain unchanged so the history still reflects what happened at the time.

My Task is scheduled after its deadline

That is allowed. Harmonise may show a warning, but the Task remains valid and saving is not blocked. Move the Scheduled Date or Scheduled Date and Time earlier only if you want the planned work to happen before the deadline.

A file is not available yet

Files need an internet connection to upload or update, and they become available only after processing finishes successfully. The Task’s other eligible core changes may still be saved separately.

A linked Task did not appear on earlier Events

Check which Event attachment choice you used:

• This event only adds the Task only to the selected Event.
• This and future events starts from the selected Event and does not add the Task to earlier Events.
• Entire series adds the Task to every eligible Event in the series, including eligible earlier Events.

Next steps

• Tasks
• Tasks linked to Events
• Recurring Events
• Sync and offline use