mirror of
https://github.com/aluxnimm/outlookcaldavsynchronizer.git
synced 2026-04-25 11:05:56 +03:00
[GH-ISSUE #423] Server returned '403' ('Forbidden') for update, trying Delete and Recreate instead... #874
Labels
No labels
1.0
1.0
1.0
2.0
Feature
Feature request
Google
Google Calendar
async
attachement
auto-migrated
auto-migrated
auto-migrated
bug
critical
enhancement
help wanted
implemented
pull-request
solved
solved
sourceforge
sourceforge
sourceforge
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/outlookcaldavsynchronizer#874
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Nick2253 on GitHub (May 30, 2024).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/423
I'm having an issue between Outlook and Gmail sync that's creating the following error:
In particular, this appears to happen any time I accept events through my Gmail calendar, or add guests to an event through my Gmail calendar (whether through the web interface, or on my phone, etc).
In particular, this creates a huge problem, because anytime that this occurs, the inviter or the guests receieve a cancellation notice from me, even though it still shows everything fine on my side.
If I accept events through my Outlook calendar, this doesn't happen.
As an example, I create an event "Test" on my Google calendar through the web interface. I then invite someone to that event. They will receive the invitation. I then synchronize calendars. Sometimes, it will synchronize just fine for a while, but before too long, I'll get the above error, which will send out the cancellation notices.
I have a debug log for this, as well as the full synchronization report, but because of PII, I don't want to post it publicly.
The relevant (I think) section of the log is reproduced below (with PII replaced; uuuu is my username, and xxxx, yyyy are the respective event numbers):
Edit: may be related to #382, #335