Recurring events and scheduling conflicts
Create a series while retaining control over dates, programs and separate lineup responses.
A recurrence creates separate events
Recurrence lets you prepare multiple dates from one program and lineup. Each occurrence is a separate event with its own date, program and people's responses. Confirming the first does not confirm the entire series.
Recurrence is a property of an event or series. An event template stores a model of content and duration but does not itself schedule further dates. Separate the decision about what should repeat in the program from the decision about when it happens.
Prepare a series
The supported range is two to fifty-two occurrences. An event already belonging to a series cannot be used to layer a second recurrence on top.
- Create an event with the correct date, time and template.
- Expand recurrence settings or choose to enable a series for an existing event.
- Choose an available frequency and occurrence count; the count includes the first date.
- Check the time zone and dates, especially around daylight saving changes or month-end.
- Confirm and review the resulting dates in the calendar.
Daylight saving changes and shorter months
A series preserves the local time in its own time zone, including transitions between standard and daylight saving time. In a monthly series, a day missing from a shorter month falls on that month's final day. This is a reason to review the resulting dates every time.
Changing the organization's time zone does not automatically rewrite the zones of series created earlier. If your group changes where it works, check existing events separately. Do not assume one setting change will move every scheduled instant as you expect.
Why saving may be rejected
When creating or rescheduling an event, the app checks for overlapping reserved intervals. In an organization using teams, team context matters when separating conflicts. A shared person may receive a conflict indicator between events without unavailable details being disclosed.
If an occurrence conflicts, adjust the range or date according to the message. Do not assume the other dates were partially created: series creation checks the entire series. Adjacent events can touch if the earlier one ends exactly when the next begins.
Change or delete one date
Editing an individual event does not automatically change the whole series. If you add a one-off note, adjust the time or delete a date, verify the action's scope in the form and confirmation. Do not treat series membership as permanent program inheritance.
When deleting several plans, deliberately select their titles and dates. Unselected events, source songs and templates remain separate resources. Before a bulk action, keep an overview of upcoming dates to avoid accidentally deleting all your planned work.