I run an online language school and host 5+ live classes per week as recurring community events. When a member RSVPs to ONE date, they're registered for every future occurrence of that series. There is no way for them to register for just the session they actually plan to attend - and no official way to cancel either.

This makes the RSVP feature useless for anyone running recurring events, which is exactly the use case communities are built for (weekly calls, classes, coaching sessions).

Right now my only workaround is creating every single session as a standalone event - that's dozens of manual event creations per month.

Related symptom already reported here: editing one occurrence wipes registrants for the whole series. Both point to the same root cause: registrations are stored on the series, not the occurrence.

Ask: store RSVPs per occurrence, not per series. A member registering for the Oct 7 session should be registered for Oct 7 only. Please also add a cancel-registration option for members.

Until this works, "recurring events" and "RSVP" are two features that cancel each other out.