question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong time in one specific recurring event

See original GitHub issue

OGCS Version: v2.9.0.0 Edition: Installed Sync Direction: O->G

Bug Description
I have several events in my outlook calendar that are successfully synced with Google Calendar, but I have one specific recurring event that always get a wrong datetime. In my Outlook Calendar it has scheduled for every day at 15:00, but after syncing, the recurring in Google Calendar is created for every day at 14:00. I tried to delete recurring event and to create it again and the problem persists. I have deleted the recurring event in Outlook and Google manually and then created again in Outlook and the problem persists. It occurs only with this specific event.

Steps to Reproduce the Issue

  1. Create a recurring event for every day at 15:00 in Outlook
  2. Sync with Google Calendar
  3. Check the created event with wrong time (14:00).

Any other information

  • My timezone is (UTC-03:00) Brasilia.
  • Event Configuration in Outlook image
  • Outlook Calendar event image
  • Google Calendar event image

Logs OGcalsync.log

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
robsonrosacommented, Sep 13, 2021

Hi @phw198

It worked!! 🎊 👏

I have no idea why that mapping was created. I can’t exclude that mapping, but I’ve changed to something useless:

image

Thanks!!

0reactions
phw198commented, Feb 26, 2022

the Outlook time zone is UTC-07:00 but the Google time zone is GMT+00:00

That’ll be your problem then. OGCS should be able to detect that Outlook is UTC-7 and convert that to an IANA timezone eg America/Denver. But it’s not and it’s getting set to GMT (and the time changed instead no doubt), which is clearly wrong and would result it poor/non-existant DST calculation.

Without a log file though I would not be able to troubleshoot further and it will be specific to your invitation and Windows config as to the particular issue. That said, pretty sure this is all catered for with the “custom timezones” I mentioned previously, but you’ve never said what version of OGCS you are running. Make sure it’s at least v2.9.0.

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Update, user action needed] Events appearing at the ...
Have the wrong times for single events, recurring events, or appointments; Update appointment schedules incorrectly; Affect RSVP responses for ...
Read more >
Recurring event times wrong by 1 hr only in iOS calendar
I just noticed that all my recurring events seemt to be one hour later in the Calendar app on my iPhone (iOS 5.1)....
Read more >
Recurring events still showing the wrong time -
When I add a reoccurring event with a start time of 2.30pm it shows up as 1.30pm. This is a real problem as...
Read more >
Calendar shows wrong times for recurring entry - Plugins
So it seems that the individual events are shown correctly, but the recurring event is always shown an hour early. How can this...
Read more >
Incorrect events times
Sometimes after synchronization with Google Calendar the times of the events are displayed incorrectly. Usually such problems are caused by the Google Calendar ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found