Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

O->G - Expired Recurring Meeting, instance moved to after expiration date doesn't sync #2046

Open
griffithska opened this issue Jan 16, 2025 · 0 comments
Labels
bug Something's not working right

Comments

@griffithska
Copy link

Checklist:-

  • Upgrade to the latest release (alpha if available) latest release
  • Reproduce the issue
  • Complete the information below
  • Provide your OGcalsync.log file (see how-to)

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

  1. Create recurring meeting with an end date
  2. Sync OGCS
  3. 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.
  4. Sync OGCS, any instances after the end date will be removed but should not be.

📎 Log file emailed

@griffithska griffithska added the bug Something's not working right label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something's not working right
Projects
None yet
Development

No branches or pull requests

1 participant