Recurring Event Disappears - Tallgrass
complete
Kimberley Busato
Tallgrass reported that when rescheduling the first screening(s) in a recurring event that the events disappeared when they were saved.
Melanie said, "Who Can See Forever is moved to tomorrow due to storms and when I went to edit the date there is an error and now it is gone. But there are tickets in both events. Help!"
In a subsequent reply, she added, "Was repeat (two screenings) set for today. I went to change them to 4/28 and there was an error on screen ( I don't remember what it was) and now they are gone."
Searching for the events, I found events with the following ids that were no longer accessible in the dashboard... selecting each of these event titles resulted in a page with a spinning wheel... similar behaviour as when you try to access a deleted event:
The corresponding event ids are:
662d4fc070bca600669ac913
65f860addb0bb50039be8d3a
65f85fa3efaa8803bd03e0db
65e7c85fbe006100482b5b37
65e7c7e826fbf10040e7558d
Link to Slack --> https://eventiveteam.slack.com/archives/C018EML35BR/p1714247054007379
To keep this more organized, tests will each be added as their own response to this thread.
godlink to test event bucket --> https://admin.eventive.org/event_buckets/610162862c12c200616a8cee/events?_god_become_user=6086c26f92857b003011dbd1
To test, I created a recurring event with a 1 month long recurrence period (May 16, 2024 to June 16,2024) with screenings on Tuesdays and Thursdays (image 1) - this created a series of 9 events (image 2).
The Event IDs for the events are as follows:
5/16/2024 19:00 --> 6638ed5bdb195b0093858ff0
5/21/2024 19:00 --> 6638ed6b7e542f0056af727b
5/23/2024 19:00 --> 6638ed6b7e542f0056af727c
5/28/2024 19:00 --> 6638ed6b7e542f0056af727d
5/30/2024 19:00 --> 6638ed6b7e542f0056af727e
6/4/2024 19:00 --> 6638ed6b7e542f0056af727f
6/6/2024 19:00 --> 6638ed6b7e542f0056af7280
6/11/2024 19:00 --> 6638ed6b7e542f0056af7281
6/13/2024 19:00 --> 6638ed6b7e542f0056af7282
Log In
Kimberley Busato
complete
Kimberley Busato
solved (uba)
Kimberley Busato
This was resolved by Andrew as part of Bug Bash Day on May 10th 2024.
There is now a validation step that must be passed in order to save the recurrence schedule. If the Showtime doesn't occur during the run of the event, then the following error is displayed.
Kimberley Busato
Test 6: Still working with a copy of the Tallgrass setup with an event recurring once in the same day.
GL to test event --> https://admin.eventive.org/event_buckets/610162862c12c200616a8cee/events/66391562336433004f3fa19b/edit?_god_become_user=6086c26f92857b003011dbd1
This time I tried editing the event through the recurrence schedule.
I changed the first day of run and last day of run, but nothing else... was hoping that the mismatch between the first and last day of run and the days of the week (image 1) might make the events disappear... it did (image 2).
The event and it's recurrence disappeared from my list of events (image 3)... Event that is missing is called Another Same Day Recurring Event.
This could be the problem... or at least part of the problem... rather than allowing me to save this test, it would be preferable if the system presented an error saying that there is a mismatch between the start and end date and the desired day of the week for the event to recur on.
cc: Chris Ethridge does this look / sound familiar or plausible with the Tallgrass situation from the other week?
Kimberley Busato
Test 5: Going back to the Tallgrass setup for additional clues...
The recurrence period for the original events appears to be within the same day (image 1)
GL to Tallgrass Event --> https://admin.eventive.org/event_buckets/619c1d24bb29830069208caa/events/65f85fa3efaa8803bd03e0db/edit?_god_become_user=5ee108082ed5c20030d6202b
I set up a similar event (image 2)
GL to my test event --> https://admin.eventive.org/event_buckets/610162862c12c200616a8cee/events/663914bd6b47310032c187f7/edit?_god_become_user=6086c26f92857b003011dbd1
Tried rescheduling this event for 24 hours later by changing the dates associated with start time and end time... edited all events... the change saved successfully, but the change was only applied to the initial event... moving it from may 16 at 5pm to May 17 at 5pm (image 3)... the fact that the second event in the sequence wasn't changed should be looked at to consider whether that's expected behaviour given that the event start and end time were edited rather than the recurrence schedule.
Returned first event back to it's originally scheduled time and tried making the same change, but this time editing "this event only"... no difference... saved successfully and the change only applied to the first event... however, since the edit was applied to this event only, this would be expected behaviour.
Still baffled.
Kimberley Busato
Test 4: Edit first event by editing the start time (5/23/2024 19:00 --> 6638ed6b7e542f0056af727c).
As per the Tallgrass conversation, I scheduling this event for 24 hours later. I applied this change to the first event only.
The change applied successfully and the first event in the recurrence sequence was moved from Thursday May 23 to Friday May 24.
Any other variations to test? I'm baffled.
Kimberley Busato
Test 3: Edit first event by editing the recurrence period to start 1 week later.
I missed screenshotting the recurrence period settings, but I changed the "First day of Run" to May 23rd.
Encountered the following error (image 1) followed by a spinning wheel (image 2); however, when I returned to the list of events, only 3 recurring events remained with the following ids:
5/23/2024 19:00 --> 6638ed6b7e542f0056af727c
5/28/2024 19:00 --> 6638ed6b7e542f0056af727d
5/30/2024 19:00 --> 6638ed6b7e542f0056af727e
Though the error message and the spinning wheel are distressing, it appears that this is actually expected behaviour as the remaining events are the ones dated May 23 & onwards.
Kimberley Busato
Test 2: Edited an event that is later in the recurrence sequence to further shorten the recurrence period by one week (5/28/2024 19:00 --> 6638ed6b7e542f0056af727d).
After editing the recurrence period, the following ids remained:
5/16/2024 19:00 --> 6638ed5bdb195b0093858ff0
5/21/2024 19:00 --> 6638ed6b7e542f0056af727b
5/23/2024 19:00 --> 6638ed6b7e542f0056af727c
5/28/2024 19:00 --> 6638ed6b7e542f0056af727d
5/30/2024 19:00 --> 6638ed6b7e542f0056af727e
This appears to be expected behaviour.
Kimberley Busato
Test 1: Shorten the recurrence period to by 1 week. I did this by editing the recurrence period in the first event (5/16/2024 19:00 --> 6638ed5bdb195b0093858ff0) (image 3). The changes saved successfully and the number of recurring events was reduced to 7.
The event ids that were retained were:
5/16/2024 19:00 --> 6638ed5bdb195b0093858ff0
5/21/2024 19:00 --> 6638ed6b7e542f0056af727b
5/23/2024 19:00 --> 6638ed6b7e542f0056af727c
5/28/2024 19:00 --> 6638ed6b7e542f0056af727d
5/30/2024 19:00 --> 6638ed6b7e542f0056af727e
6/4/2024 19:00 --> 6638ed6b7e542f0056af727f
6/6/2024 19:00 --> 6638ed6b7e542f0056af7280
This appears to be expected behaviour.