You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Description
I have a recurring meeting from my boss that occurs every Tuesday since July with an end date of Tuesday January 14th. My boss rescheduled the Jan 14th to Thursday Jan 16th and it was removed from my Google calendar and will not sync. I was able to confirm that setting the Date Range from 1 Day in the past to 7 Days in the past (prior to the end date of the recurring schedule) the meeting did sync again. I understand this may be a technical limitation of how recurring schedules are handled, but ideally the event would stay on the calendar as the specific instance is still within the date range for OGCS to sync.
Steps to Reproduce the Issue
Create recurring meeting with an end date
Sync OGCS
Reschedule the last (possibly any) of the instances to a date later than the end date of the recurring schedule but also further in the past than the OGCS "Days in the past" setting.
Sync OGCS, any instances after the end date will be removed but should not be.
📎 Log file emailed
The text was updated successfully, but these errors were encountered:
OGCS Version: v2.11.10
Edition: Installed
Sync Direction: O->G
Bug Description
I have a recurring meeting from my boss that occurs every Tuesday since July with an end date of Tuesday January 14th. My boss rescheduled the Jan 14th to Thursday Jan 16th and it was removed from my Google calendar and will not sync. I was able to confirm that setting the Date Range from 1 Day in the past to 7 Days in the past (prior to the end date of the recurring schedule) the meeting did sync again. I understand this may be a technical limitation of how recurring schedules are handled, but ideally the event would stay on the calendar as the specific instance is still within the date range for OGCS to sync.
Steps to Reproduce the Issue
📎 Log file emailed
The text was updated successfully, but these errors were encountered: