5h ago

Evergreen rule to respect current event days

I want to make a 4 day event Evergreen and keep the current timings. I want to repeat the event every 1 month, starting on the first Monday of the month. Using the wonderful new “select all feature” works for day 1 of the event, but the other days all end up on day 1 too because they are all being placed on the first Monday of the next month. Can we add a toggle to somehow respect the current days (separation)? I can’t workaround this by selecting each day and programming the Evergreen settings 4 times because for example, in Jan, my day 4 would start before my day 1 (first Thursday in Jan is before the first Monday). Also, please know that the fast forward button mouseover guidance (manually update to next) defaults to UK time.

Reviewing

4 hours ago

Thanks for raising this, it’s a smart feature request, and we can see how it would make month-to-month evergreen scheduling much smoother. That said, keeping every talk’s relative spacing intact while handling edge cases (weekends, months with different lengths, varying weekday positions, etc.) adds quite a bit of complexity. We want to avoid rushing such a foundational change and potentially causing unexpected conflicts for existing events. For now, the safest approach is to use bulk auto-repeat updates a day at a time - select all talks from day 1, apply the desired rule, then repeat for day 2, and so on. That keeps the intended mix of dates and times without losing control over each day’s placement. We’ll keep tracking interest in this idea as we continue evolving evergreen scheduling. Thanks also for the heads up about the tooltip date showing in London time zone. We'll roll out a patch to resolve that in the next few hours.

4 hours ago

Hi Ben, I can certainly understand that you can’t do everything everybody wants at once and need to make choices and it is great that you are respecting current setups and don’t want to mess those up. I do however think that this request is rather central to what Evergreen programming should do. Hopefully the following will help when you do get around to looking at Evergreen in greater depth. As I mentioned in my previous comments, the bulk-auto repeat one day at a time does not work in this case. Current settings: Day 1: 1 Dec (Mon) Day 2: 2 Dec (Tue) Day 3: 3 Dec (Wed) Day 4: 4 Dec (Thu) Day 5: 5 Dec (Fri) What we want: Program runs as per above, starting on the first Monday of the month every month. What happens with bulk-auto repeat one day at a time: In the settings: Day 1 - set to repeat first Monday monthly Day 2 - set to repeat first Tuesday monthly Day 3 - set to repeat first Wednesday monthly Day 4 - set to repeat first Thursday monthly Day 5 - set to repeat first Friday monthly What we get: Day 1: 5 Jan (Mon) As intended Day 2: 6 Jan (Tue) As intended Day 3: 7 Jan (Wed) - Day 3 now plays before Day 1 & 2 Day 4: 1 Jan (Thu) - Day 4 now plays before Day 1, 2 & 3 Day 5: 2 Jan (Fri) - Day 5 now plays before Day 1, 2 & 3 There is now the option to choose the first Weekday of the month. However, this still does not give us what we want - if the first weekday is a Wednesday Day 1 will be a Wednesday. It’s certainly better than the above option, but does not achieve the simple objective of a 5-day Evergreen event running monthly over 5 consecutive days, starting on the first Monday of the month.

4 hours ago

Hey there Cynthia, thank you so much for the extra info. Massively appreciated. I totally get that in this particular case, if your programming is based on the first specific day of a month, that it is, of course, possible that edge cases could transpire whereby the first Monday is different from the first Wednesday etc. And that won't necessarily create things in the sequence that you're looking for. This is a good example of an edge case that points to a more substantial rethinking being needed around how evergreen capabilities work in the bulk editing scenario. All being well, we'll be able to get to this in the future, and so it will be useful to be able to refer back to this use case. Thanks again, really appreciate the feedback.