[GH-ISSUE #353] When I change a monthly schedule with CalDAV Synchronizer, it becomes a weekly schedule. #1239

Closed
opened 2026-03-14 00:45:11 +03:00 by kerem · 1 comment
Owner

Originally created by @eungmo on GitHub (Apr 12, 2022).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/353

Hi, I'm a CalDAV server developer.

  1. I created 2022-04-07 monthly schedule (First Thursday) from my program.
  • started_at: 2022-04-07 18:30:00
  • endedAt: 2022-04-07 20:00:00
  • frequency: monthly
  • interval: 1
  • byday: 1TH (meaning every 1st Thursday of the month)
  1. After I only changed the schedule's subject with CalDAV Synchronizer, it becomes like that.
  • started_at: 2022-04-07 18:30:00
  • endedAt: 2022-04-07 20:00:00
  • frequency: monthly
  • interval: 1
  • byday: TH (meaning every Thursday)

So, it looks like a weekly schedule.
Could someone help me how I can handle it?
Will I ignore invalid "byday" change?

Originally created by @eungmo on GitHub (Apr 12, 2022). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/353 Hi, I'm a CalDAV server developer. 1. I created 2022-04-07 monthly schedule (First Thursday) from my program. - started_at: 2022-04-07 18:30:00 - endedAt: 2022-04-07 20:00:00 - frequency: monthly - interval: 1 - byday: **1TH** (meaning every 1st Thursday of the month) 2. After I only changed the schedule's subject with CalDAV Synchronizer, it becomes like that. - started_at: 2022-04-07 18:30:00 - endedAt: 2022-04-07 20:00:00 - frequency: monthly - interval: 1 - byday: **TH** (meaning every Thursday) So, it looks like a weekly schedule. Could someone help me how I can handle it? Will I ignore invalid "byday" change?
kerem closed this issue 2026-03-14 00:45:16 +03:00
Author
Owner

@eungmo commented on GitHub (Jun 14, 2022):

I solved this issue.
My CalDAV server is ignoring recurrence rule change with this kind of condition.

  • frequency: monthly
  • byday: TH

Because the "monthly TH" recurrence rule does not make sense.

<!-- gh-comment-id:1154737851 --> @eungmo commented on GitHub (Jun 14, 2022): I solved this issue. My CalDAV server is ignoring recurrence rule change with this kind of condition. - frequency: monthly - byday: TH Because the "monthly TH" recurrence rule does not make sense.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/outlookcaldavsynchronizer#1239
No description provided.