Recurring sessions with a start and an end

Fictional example: training Tuesday and Thursday 18:00–19:00, 3 November to 17 December 2026, Europe/Madrid. A monthly workshop has another rule and needs a separate entry.

State what each recurrence means. “Every month” is not “the second Tuesday each month”: the current editor does not offer every standard pattern. Use specific dates when one cannot be expressed.

Choose weekly, Tuesday/Thursday, times and period in the review. Confirm the first date belongs to a planned day and recurrence ends where intended. Add a location and reminder if useful.

Do not exclude public holidays without knowing whether the activity is cancelled. For a specific rest week, split blocks or list sessions: there is no free per-date exception editor.

Once correct, create and add the subscription. For a fixed season that will never change, you can import the file, knowing that copy will not update later.

For a group schedule, omit medical details and participant personal information. A change at the source arrives when the client checks the feed, not necessarily before the next session.

For a permanent time change, edit the existing calendar entry. For a one-off cancellation, check how to split the period before changing every week. Do not create an identical subscription to correct one event.

At season end, check there are no future repetitions. Removing a subscription from your device and deleting the original are different actions; choose the appropriate one and retain only needed copies.