Google calendar missing items or showing wrong times

kopd42

Time zone issues would make sense with my work calendar. I’m in Central time, the company office is on the East Coast, and a meeting series on my calendar which is messed up is from a client on Mountain time. Still, some events are fine. Maybe it depends on who at HQ schedules it. Don’t know. The personal calendar is on local time, so I’m not sure why one or two events in it would behave differently than others. I’ve pulled the ics files and stripped each down to a handful of events with comments about whether or how they were affected.

First the personal calendar:

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:[snip]
X-WR-TIMEZONE:America/Chicago
BEGIN:VTIMEZONE
TZID:America/Chicago
X-LIC-LOCATION:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
TZNAME:CDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART:20230118T223000Z
DTEND:20230118T233000Z
DTSTAMP:20230117T220752Z
UID:
CREATED:20221024T220526Z
LAST-MODIFIED:20221024T220526Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:******correct time and date ******
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Chicago:20230116T180000
DTEND;TZID=America/Chicago:20230116T193000
DTSTAMP:20230117T220752Z
UID:
RECURRENCE-ID;TZID=America/Chicago:20230116T180000
CREATED:20221221T030016Z
DESCRIPTION:
LAST-MODIFIED:20230116T194802Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:******event did not show up******
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Chicago:20230118T190000
DTEND;TZID=America/Chicago:20230118T200000
DTSTAMP:20230117T220752Z
UID:
RECURRENCE-ID;TZID=America/Chicago:20230111T190000
CREATED:20220608T143754Z
DESCRIPTION:
LAST-MODIFIED:20221215T014714Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:******time shows one hour late, 2000 central instead of 1900 ******
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

Now the work calendar:

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:
X-WR-TIMEZONE:America/Chicago
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:19700308T020000
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:19701101T020000
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20230119T093000
DTEND;TZID=America/New_York:20230119T100000
RRULE:FREQ=WEEKLY;BYDAY=TH
DTSTAMP:20230117T222720Z
ORGANIZER;CN=
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=
CREATED:20230105T145218Z
DESCRIPTION********** incorrectly shows up one hour early (0730 central, should be 0830 central) **********
LAST-MODIFIED:20230112T142204Z
LOCATION:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Architecture / T&M - Stand Down
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20230119T120000
DTEND;TZID=America/New_York:20230119T123000
DTSTAMP:20230117T222720Z
ORGANIZER;CN=
UID:
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;CN=
RECURRENCE-ID;TZID=America/New_York:20230119T120000
CREATED:20221025T182902Z
DESCRIPTION:********** correctly says 1100 central Thursday **********
LAST-MODIFIED:20230117T214824Z
LOCATION:
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:____________________
TRANSP:OPAQUE
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20230118T100000
DTEND;TZID=America/New_York:20230118T110000
RRULE:FREQ=WEEKLY;BYDAY=WE
DTSTAMP:20230117T222720Z
ORGANIZER;CN=
UID:
CREATED:20220106T213303Z
DESCRIPTION:********** correctly says Wednesday 0900 Central *************
LAST-MODIFIED:20230117T121014Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Developer Weekly Training
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
BEGIN:VEVENT
DTSTART;TZID=America/Phoenix:20220516T090000
DTEND;TZID=America/Phoenix:20220516T093000
RRULE:FREQ=WEEKLY;WKST=SU;UNTIL=20230203T160000Z;INTERVAL=1;BYDAY=MO,TU,WE,
 TH,FR
EXDATE;TZID=America/Phoenix:20221226T090000
EXDATE;TZID=America/Phoenix:20221223T090000
EXDATE;TZID=America/Phoenix:20221125T090000
EXDATE;TZID=America/Phoenix:20221124T090000
DTSTAMP:20230117T222720Z
ORGANIZER;CN=
UID:[numbers]
CREATED:20230113T160615Z
DESCRIPTION: ********* Incorrectly shows up one hour late, as 1100 Central instead of 1000 central ************
LAST-MODIFIED:20230113T172431Z
LOCATION:Microsoft Teams Meeting
SEQUENCE:34
STATUS:CONFIRMED
SUMMARY:____ Daily Standup
TRANSP:OPAQUE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-APPT-SEQUENCE:34
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-OWNERAPPTID:-
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MICROSOFT-DONOTFORWARDMEETING:FALSE
X-MICROSOFT-LOCATIONS:
END:VEVENT
END:VCALENDAR

sdetweil

@kopd42 i need the UID values from all those…

recurrence-ID values mean that one element of a recurring event was changed… but it needs to connect to the UID of the original event description…

and those events with rrule are not in this list of events…

kopd42

@sdetweil Okay, I’ll send the file directly. It’s large and pulling out all the personal info would be a chore.

sdetweil

@kopd42 u can send it to my email… same userid at gmail

sdetweil

@kopd42 interesting one

the rrule is

{
  "rrule": {
    "_cache": {
      "all": false,
      "before": [],
      "after": [],
      "between": []
    },
    "origOptions": {
      "tzid": "America/New_York",
      "dtstart": "2023-01-19T14:30:00.000Z",
      "freq": 2,
      "byweekday": [
        {
          "weekday": 3
        }
      ]
    },
    "options": {
      "freq": 2,
      "dtstart": "2023-01-19T14:30:00.000Z",
      "interval": 1,
      "wkst": 0,
      "count": null,
      "until": null,
      "tzid": "America/New_York",
      "bysetpos": null,
      "bymonth": null,
      "bymonthday": [],
      "bynmonthday": [],
      "byyearday": null,
      "byweekno": null,
      "byweekday": [
        3
      ],
      "bynweekday": null,
      "byhour": [
        14
      ],
      "byminute": [
        30
      ],
      "bysecond": [
        0
      ],
      "byeaster": null
    }
  }
}

details

[17.01.2023 18:37.29.125] [DEBUG] start: Thu Jan 19 2023 08:30:00 GMT-0600 (Central Standard Time)
[17.01.2023 18:37.29.125] [DEBUG] end:: Thu Jan 19 2023 09:00:00 GMT-0600 (Central Standard Time)
[17.01.2023 18:37.29.125] [DEBUG] duration: 1800000

then we ask for dates between

[17.01.2023 18:37.29.126] [DEBUG] Search for recurring events between: Tue Jan 17 2023 18:37:29 GMT-0600 (Central Standard Time) ( now) and Tue Jan 16 2024 23:59:59 GMT-0600 (Central Standard Time)

and get back, for central time

with dates: ["2023-01-19T13:30:00.000Z","2023-01-26T13:30:00.000Z","2023-02-02T13:30:00.000Z","2023-02-09T13:30:00.000Z","2023-02-16T13:30:00.000Z","2023-02-23T13:30:00.000Z","2023-03-02T13:30:00.000Z","2023-03-09T13:30:00.000Z","2023-03-16T13:30:00.000Z","2023-03-23T13:30:00.000Z","2023-03-30T13:30:00.000Z","2023-04-06T13:30:00.000Z","2023-04-13T13:30:00.000Z","2023-04-20T13:30:00.000Z","2023-04-27T13:30:00.000Z","2023-05-04T13:30:00.000Z","2023-05-11T13:30:00.000Z","2023-05-18T13:30:00.000Z","2023-05-25T13:30:00.000Z","2023-06-01T13:30:00.000Z","2023-06-08T13:30:00.000Z","2023-06-15T13:30:00.000Z","2023-06-22T13:30:00.000Z","2023-06-29T13:30:00.000Z","2023-07-06T13:30:00.000Z","2023-07-13T13:30:00.000Z","2023-07-20T13:30:00.000Z","2023-07-27T13:30:00.000Z","2023-08-03T13:30:00.000Z","2023-08-10T13:30:00.000Z","2023-08-17T13:30:00.000Z","2023-08-24T13:30:00.000Z","2023-08-31T13:30:00.000Z","2023-09-07T13:30:00.000Z","2023-09-14T13:30:00.000Z","2023-09-21T13:30:00.000Z","2023-09-28T13:30:00.000Z","2023-10-05T13:30:00.000Z","2023-10-12T13:30:00.000Z","2023-10-19T13:30:00.000Z","2023-10-26T13:30:00.000Z","2023-11-02T13:30:00.000Z","2023-11-09T13:30:00.000Z","2023-11-16T13:30:00.000Z","2023-11-23T13:30:00.000Z","2023-11-30T13:30:00.000Z","2023-12-07T13:30:00.000Z","2023-12-14T13:30:00.000Z","2023-12-21T13:30:00.000Z","2023-12-28T13:30:00.000Z","2024-01-04T13:30:00.000Z","2024-01-11T13:30:00.000Z"]

all still good.

but there is a recurrence entry for 20230119, but not in the ics
recurrence overrides cal entry (aka meaning it was modified outside the cycle, but… I don’t see it in the data )

[17.01.2023 18:37.29.144] [DEBUG] event.recurrences: [object Object]
[17.01.2023 18:37.29.144] [DEBUG]  recurring date is Thu Jan 19 2023 07:30:00 GMT-0600 (Central Standard Time) offset is 360
[17.01.2023 18:37.29.145] [DEBUG]  recurring date is Thu Jan 19 2023 07:30:00 GMT-0600 (Central Standard Time) offset is 6 Hour is 07
[17.01.2023 18:37.29.145] [DEBUG] Corrected startDate: Thu Jan 19 2023 07:30:00 GMT-0600 (Central Standard Time)

all this data is from code thats not ours… parser or rrule

will keep investigating

sdetweil

actually I think this is our good friend rrule.between again…

the event time is STILL 14:30 UTC time… not 13:30.

sdetweil

@kopd42 sent you file in email w maybe fix

shizzlesticks

I’ve had some similar issues with Google Calendar data and I’ve had to delete and recreate some events that are strange. Some birthdays (recurring yearly all-day events) seemed to be the most problematic, but I had a simple one-time event be off by an hour last week. Removing and recreating is what I had to do to get it fixed.

sdetweil

@shizzlesticks I’ve seen some recurrent events in the ics that don’t work, but move the yearly to the end of the rule, and all is well. not our code. .

haven’t come up with a solid cure yet