Open mfleonhardt opened 2 years ago
:package: Trying my luck with a quick hotfix v2.9.4.9.zip (see instructions for applying).
Please let me know how it goes!
Thanks for that. I see a change in the appointment time now. It's no longer attempting to move the start time pre-DST. However, it still is trying to move the start date and being met with the 400 error response.
The same 3 events are all still experiencing the error and seem to have the common factor of being recurring events that began prior to the start of DST.
:package: Thanks for the quick testing - could you please apply patch v2.9.4.11.zip (see instructions for applying) which has some extra logging and should help me determine what's happening.
Patched and re-synced (with error). Log attached.
I've done lots of testing but simply can't replicate this!
:package: Could we try that again with v2.9.4.12.zip (see instructions for applying) - again, further logging...and with any luck it might actually work.
If you could upload you log again even if it does work, please.
No change in behavior.
FYI, I'm doing some work travel for the next couple weeks. I may not be able to reply very quickly. (Back from travel and able to respond again)
This issue has been marked dormant because the last update is at least 30 days ago. If no update is made with the next 7 days, the issue will be closed.
I've captured all the start and ends dates which can be seen in your logs and I really can't see the problem, nor can I replicate the error.
If you're game, I think we need to extract the definition of the Google calendar item in a JSON format:
Alternatively, you might be able to click on the event menu and then "Publish event" and with this link I could duplicate it to my own calendar to troubleshoot - I've not tried this before though!
Unfortunately, the events that were causing this are no longer on my calendar. I am no longer having this issue when I perform the sync. I would have to wait until another recurring event gets scheduled that has the same issue.
It is probably safe to close this issue for now. If it happens again, I can reopen with the extracted Google cal item definition as you described.
Sounds good @mfleonhardt - I will keep an eye out for any updates
:thought_balloon: Will see if I can automatically log the Event as a JSON object to troubleshoot further...
This issue has been marked dormant because the last update is at least 30 days ago. If no update is made with the next 7 days, the issue will be closed.
:package: Please apply hotfix v2.9.7.3.zip (see instructions) and upload your OGcalsync.log file after reproducing the error.
This issue has been marked dormant because the last update is at least 30 days ago. If no update is made with the next 7 days, the issue will be closed.
So I think I've worked out a way of replicating this problem:
[1] This effectively creates a new recurring series from that date, but Outlook doesn't have that concept and the two series are now essentially incompatible.
Getting OGCS to handle this will certainly be non-trivial. #1910 makes a start...
:package: To assist troubleshooting thie issue, please apply hotfix v2.9.7.3.zip (see instructions and make sure you are running at least v2.9.7.0 first) and upload your OGcalsync.log file after reproducing the error.
Probably same issue as #1196 and #837
OGCS Version: v2.9.4 Edition: Installed Sync Direction: O<->G (during the O -> G portion)
Bug Description
Appears to occur when syncing recurring events from Outlook --> Google attempting to change the start time for events in the distant past. The trigger for this behavior seems to have been the DST change.
Steps to Reproduce the Issue
I don't know how to create new calendar events that will reproduce this issue, but the same 3 calendar events cause this error reliably on every sync.
Any other information
OGcalsync.log