We are using Looping to create calendar events that are a monthly virtual series - that part works fine. When people register, there’s another Zap that creates the entire series (via looping) and writing back all the series dates to a multi-instance panel in our AMS for participants’ easy access to the meeting URL for each recurrence - this is great for registrations before the entire series begins, but people may register to join the recurring event at any point in the series.
My question: How can I make sure that only “future” events in the series get created (and not the entire loop)?
Example: the original event has the code: ANA22
The subsequent events in the series become: ANA222, ANA223, ANA224, ANA225 (etc.)
If someone registers for ANA223, how can only the subsequent events (ANA224, ANA225, etc) in the loop be created? Having the loop run the entire series with past events is a waste of valuable zaps!