Recurring Events
Repeat a commitment, then choose which Event occurrences later changes should affect.
Show instructions for
Recurring Events are for commitments that return on a predictable pattern.
You might create one for Sunday football, a weekly project review, a monthly appointment, or an annual birthday. Harmonise keeps the series connected while still allowing one occurrence to be changed without rewriting every other date.
When should an Event repeat?
Use repeat when the same commitment returns on a regular schedule.
| Event | Useful repeat pattern |
|---|---|
| Sunday football | Every Sunday |
| Project review | Every Monday |
| Monthly accounts meeting | First weekday of every month |
| Birthday | Every year |
Use separate Events when the dates do not share a real pattern or need unrelated details.
A recurring Event starts with one occurrence
The first Event supplies the starting date, time, calendar, timezone, and usual details for the series.
For example:
Project review
- Date and Time: Monday at 10:00-11:00 AM
- Repeat: Every Monday
- Calendar: Work
- Reminder: 15 minutes before
Each occurrence uses the series details until you change that occurrence or a wider part of the series. Every Event has one immutable IANA timezone, selected when it is created. Moving an occurrence does not change the Event timezone.
Occurrence identity
Each occurrence belongs to its Event series and has a position that Harmonise uses when applying an edit or deletion scope. If that occurrence or series information is unavailable, Harmonise may offer fewer choices rather than risk changing the wrong Event.
Create a recurring Event
On mobile
- Open the Create menu and choose Event.
- Enter the Event title and choose a writable calendar.
- Set the first occurrence’s timed or all-day dates.
- Open Repeat and choose how often the Event should return.
- Choose when the series should end.
- Add a location, description, reminders, or linked Tasks when they help.
- Choose Create.
On web
- Choose Create, then choose Event.
- Enter the title, choose a writable calendar, and set the first occurrence.
- Choose Daily, Weekly, Monthly, or Yearly under Repeat.
- Add a location, description, reminders, or linked Tasks when they help.
- Choose Create event.
Web-created repeat rules currently use no end date. Use mobile when you need a custom interval, selected weekdays, or a defined ending.
Choose how often it repeats
Harmonise supports daily, weekly, monthly, and yearly patterns.
Common choices include:
- Every day
- Every Week on Monday
- Every Third Monday of the Month
- Every 25th of the Month
- Every year on the Dec 25th
- Custom
On mobile, choose how the series ends:
- Never — continues until you stop it.
- On date — stops on the selected date.
- After — stops after the selected number of occurrences.
Choose which Events a change should affect
When you edit or delete a recurring Event, Harmonise asks which occurrences should be affected when the requested scope is safe.
Only this occurrence
Choose Only this occurrence when the change is an exception.
Examples:
- Move this Monday’s review to Tuesday.
- Use a different room this week.
- Change or remove this occurrence’s reminder.
- Delete one occurrence because the meeting is not needed this time.
The selected occurrence can become detached from the series so its custom details remain independent. Earlier and later occurrences continue to use the series defaults.
This and following occurrences
Choose This and following occurrences when the commitment changes from the selected occurrence onward.
Examples:
- Move the weekly review from Monday to Tuesday from this week onward.
- Change the usual time for future occurrences.
- Change the calendar or location from this occurrence onward.
- End or replace the repeat pattern from this point forward.
Earlier occurrences remain on the original series. The selected and later occurrences use the successor series.
Entire series
Choose Entire series when the change belongs to the Event series as a whole.
Examples:
- Rename the recurring Event.
- Change the usual reminder or location.
- Change the calendar.
- Replace the repeat pattern or ending.
- Delete the entire Event series.
Historical one-off exceptions are not silently rewritten unless the operation explicitly includes them.
Harmonise shows only recurrence scopes that can be applied safely. An online meeting can reduce the choices: This and following occurrences may be unavailable when the affected range contains an online meeting that cannot be safely migrated to a successor series. Some occurrence-level meeting changes support only Only this occurrence or Entire series. Provider-backed recurring Events can have additional provider-specific limits.
If a scope is unavailable, save the Event and the online meeting separately, change the meeting separately, use the provider’s application, or choose another scope that Harmonise offers.
When an occurrence moves
Moving an Event occurrence recalculates its Event reminders. It also changes every linked Task’s Event-controlled effective deadline and eligible deadline reminders.
For a timed Event, the new start becomes the linked Task’s effective Due Date and Time. For an all-day Event, the new first local date becomes its effective Due Date.
The Task’s Scheduled Date or Scheduled Date and Time does not move automatically. Scheduled-start reminders stay tied to that Task schedule. A Task schedule is allowed to remain after the Event-controlled deadline. The frontend may show a non-blocking warning, but the state remains valid and saving is not blocked.
Event reminders in a series
Each Event can have up to two active reminders. A reminder uses the Event time or a supported non-negative amount of time before it; zero means at the Event time or on the Event date, depending on the Event type. Moving an occurrence recalculates its Event reminders. Event reminders remain separate from reminders on linked Tasks, and a saved Event reminder is an alert rather than an ordinary Inbox item.
Attachments across a series
Attachments belong to the Event series collection, with up to five attachment slots, so occurrences do not have separate attachment sets. Changing or deleting only one occurrence leaves the series attachments in place. Deleting the complete series removes its Event attachments.
When This and following occurrences splits a series, the earlier source series keeps its existing attachments. The new future series starts without copied attachments. Event attachments are not copied to external calendar providers.
Online meetings and recurrence
An Event can have a physical location and an online meeting at the same time. The meeting provider, connection, Event timing, and recurrence position all affect which changes are safe. Harmonise may therefore offer fewer scopes for an Event with a managed or provider-backed meeting than for an Event without one.
When a meeting cannot be safely moved to a successor series, This and following occurrences is not offered for that change. Depending on the meeting’s position, changing only the current occurrence or the Entire series may be the supported choice. These restrictions apply only where the meeting or provider requires them, not to every recurring Event.
Managed online-meeting changes require a connection. A manually supplied HTTPS meeting link is stored with the Event and is not remotely managed by Harmonise.
Remove Event recurrence
Removing repeat is different from changing only one occurrence.
Remove repeat from this and following Events
Earlier Events and their linked Tasks remain. The selected Event becomes non-recurring, later occurrences are removed, and Tasks still linked in the selected and future affected range are deleted.
Remove repeat from the entire series
The series becomes non-recurring and every Task still linked through that Event series is deleted, including completed, historical, and customized linked Tasks. Those Tasks do not become standalone recurring Tasks or inherit the former Event repeat rule.
A Task detached or unlinked before recurrence is removed is standalone and remains.
Delete recurring Events carefully
Deleting one occurrence and deleting a series are different actions.
The Event operation supports Only this occurrence, This and following occurrences, and Entire series. Harmonise shows only a scope that is safe for the Event and its connected services.
Delete only this occurrence
Only the selected Event occurrence disappears. Every Task still linked to that occurrence is deleted. Other Event occurrences continue.
Delete this and following occurrences
The original series ends before the selected occurrence. The selected and later Events disappear, along with Tasks still linked in that affected range. Earlier Events and their linked Tasks remain.
Delete the entire series
The Event series and every Task still linked through that Event-series relationship are deleted. A detached or unlinked Task remains standalone.
The current mobile and web deletion dialogs expose Only this occurrence and Entire series. This and following occurrences is supported by the Event operation but is not currently exposed by every platform or every Event. Do not assume that it is available from the current deletion dialog. Editing a recurring Event is separate and may still offer This and following occurrences when that change is safe.
Connected-calendar limits
Provider-backed recurrence is not equally editable everywhere. Some providers require a full-series update or delete. Others allow one occurrence or the full series but do not support This and following occurrences. An imported pattern that Harmonise cannot safely interpret can also limit editing to the full series.
Harmonise shows only the scopes it can apply safely. Read-only Events cannot be changed. When the needed choice is unavailable, make the change in the calendar that owns the Event and allow it to sync back.
Saving recurring changes offline
Some eligible core Event changes can be saved locally and synchronized later. This depends on the local Event save being active, the Event belonging to a locally manageable calendar, the requested mutation being supported, and there being no conflict or other synchronization barrier. Recurrence splits, invitations, online-meeting changes, attachments, and provider-owned changes may require a connection because they have server-owned side effects.
Tasks that repeat with Events
A Task can follow a recurring Event instead of using its own Task repeat rule. When adding it, choose This event only, This and future events, or Entire series.
The Event controls which linked Task occurrences exist, their effective deadline, and their calendar. The Task keeps its own completion state, Scheduled Date or Scheduled Date and Time, reminders, subtasks, and other Task-owned details. A new linked Task adopts the Event timezone; an existing Task must already use the Event calendar, and linking or relinking aligns its stored Task timezone. The linked Task does not expose an independent timezone choice. See Events and linked Tasks for the complete workflow.
When editing an existing recurring Event-linked Task, use the Task mutation scope allowed for that field: This task, This and future tasks, or Entire series. Completion and reopening, status, taken-by state, sort order, subtask completion, Scheduled Date or Scheduled Date and Time, and scheduled-start reminders always apply only to This task.
These Task mutation scopes are different from the Event attachment choices used when the Task is first added: This event only, This and future events, or Entire series.
Common problems
I cannot choose the scope I need
The available choices depend on whether Harmonise has a safe occurrence and series reference and whether the calendar permits the requested mutation. A series record, unsupported imported pattern, detached occurrence without a usable reference, or read-only calendar can reduce the available choices.
I changed one occurrence, but future Events did not change
You probably chose Only this occurrence. Edit the Event again and choose This and following occurrences or Entire series, depending on how much of the series should change.
I changed future Events, but earlier Events stayed the same
That is expected when you choose This and following occurrences. Earlier Events remain unchanged so the calendar history reflects what happened.
A linked Task schedule did not move with the Event
That is expected. The Event changes the linked Task’s effective deadline, not its Scheduled Date or Scheduled Date and Time. A schedule after the Event-controlled deadline is valid. Harmonise may show a non-blocking warning, but saving is not blocked; reschedule the Task only if you want the planned work to happen earlier.