Meetings setup in Office and sent to external people don't actually send invite to people #1
Reference in New Issue
Block a user
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?
I can add external emails to a meeting invite, but the invite never actually sends.
Fixed and live — please verify
Root cause was not a permissions or external-recipient problem, and it was worse than the title
suggests: since 2026-06-29, saving an event with any attendee (internal or external) failed for
every user with "Failed to save event".
The 2026-06-29 attempt to fix this issue patched core Nextcloud
(
apps/dav/lib/CalDAV/Schedule/IMipPlugin.php) to send invites from the organizer's own mail account,but the patch called
$result->fetchAssociative()— a Doctrine DBAL method that doesn't exist onNextcloud's
OC\DB\ResultAdapter. That raises\Error, and the surroundingcatch (\Exception)does not catch
\Error, so the fatal escaped and killed the CalDAVPUT. The Calendar UI justshowed its generic "Failed to save event"; the real error was only ever in
data/nextcloud.log.Fix (2026-07-13):
fetch()instead offetchAssociative(), anis_array()guard, andcatch (\Throwable)so any future failure here falls back to the system mailer instead of 500-ingthe save. No restart needed (
opcache.validate_timestamps=On); it is live now.Verified:
PUTwith an attendee -> HTTP 201 (was 500)from=<johannes@bcos.cloud> to=<...> status=sent— invite goes out from the organizer'sown address, not noreply, which is what this issue asked for
@tristan — please create a meeting with an external attendee and confirm it both saves and that the
invite arrives. If Outlook desktop is slow to show it but your phone gets it, that's client-side
sync, not the send path.
Follow-up filed as #2: this patch lives only in the running container and will silently revert on the
next image bump or
--force-recreate.Correction to my note above: the follow-up is tracked in hiveiq-ops/hiveiq-devops#38 (hiveiq-ops/hiveiq-devops#38), not
bcos-office#2— that one was filed in the wrong repo and is superseded.This issue (#1) is unaffected: the fix is live, and it stays open pending @tristan's verification.