-
Notifications
You must be signed in to change notification settings - Fork 12k
Closed
Labels
reactive⚡︎🐛 bugSomething isn't workingSomething isn't working📉 regressingThis used to work. Now it doesn't anymore.This used to work. Now it doesn't anymore.
Description
Summary
When an event is configured to recur yearly for multiple iterations, only the first occurrence is ever created. No future instances appear under “Upcoming,” and no entry appears under the “Recurring” tab.
Steps to Reproduce
- Create an event type with recurrence set to yearly and specify multiple iterations (e.g. 5).
- Use that event type to create a booking (so it’s a recurring booking yearly).
- After confirming the booking, check the “Upcoming” bookings and “Recurring” tab.
- Observe that only the initial instance is present; no future occurrences or recurring metadata are shown.
Expected Result
- All scheduled yearly instances (e.g., 5 occurrences) should be generated and visible in the “Upcoming” list.
- The “Recurring” section/tab should show details of the series, including remaining occurrences and the ability to manage/cancel them.
Actual Result
- Only the first instance is created and visible.
- The “Recurring” tab shows no recurring bookings, as if recurrence was never applied.
- Future instances are not generated or displayed.
Impact
- Severity: S2 (High) — Recurrence functionality is broken for yearly events.
- Users affected: Users relying on yearly recurring events (e.g., annual appointments, subscriptions)
- Business impact: Recurring event flows cannot handle yearly schedules, reducing the product’s capability and breaking customer expectations.
Notes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
reactive⚡︎🐛 bugSomething isn't workingSomething isn't working📉 regressingThis used to work. Now it doesn't anymore.This used to work. Now it doesn't anymore.