-
Notifications
You must be signed in to change notification settings - Fork 4
Issues with zoom generated events #3
Comments
Well, strange. I don't understand why the ID should be longer just because it is a Zoom meeting, though. Splitting it into multiple email addresses would be possible, but then every ID (not just ones with long ID) need to use two attendee email addresses, or the evaluation logic will become insanely complex. I won't be able to implement that change in the foreseeable future. You might have better luck with just using v0.8 of the flow (with the disadvantage that the location is no longer synchronized). |
The strings only seem to be 232 characters. I looked up the max email length and its 254 (256 with < and >). I've just shortened the username to 'dont-delete' and that has fixed it for me. |
Glad to hear it. Keep in mind that the sync will only work properly if you adapt all Power Automate actions that parse the event ID from required-attendee fields. The code of these blocks contains this: slice(
split(item()?['requiredAttendees'], ';')[0],
43, // length of "do-not-delete-this-attendee-or-sync-breaks@"
sub(length(split(item()?['requiredAttendees'], ';')[0]), 8) // 8 is the length of ".invalid"
) |
There is now an updated flow available at https://github.com/MShekow/ng-outlook-google-calendar-sync/ which might fix your problem. The https://github.com/MShekow/outlook-google-calendar-sync flow has been deprecated and is no longer maintained. |
Running tests. I've isolated the issue with two zoom created events. Their IDs are significantly longer than the events that sync successfully.
The ones that fail return a 400 error.
As the iCalUid is being stored in the attendees I suspect the long addresses are the culprit. Perhaps it could be split over multiple attendee addresses?
The text was updated successfully, but these errors were encountered: