- Ya
- 14 Agosti 2026, 14:34 UTC
- Mwandishi
- Kamo
- Ahadi ya
- 370af5c
Callbacks were not reaching the calendar at all. This service picked the target calendar by account — findPrimaryByUser — and a user is global while a member is that user inside one organisation. An account belonging to two organisations therefore has two primary calendars, correctly, and the lookup threw "query did not return a unique result: 2". The mirror is best-effort, so SecurityService logged a warning and the callback was simply never on anyone's calendar. Three of the four callbacks in production had no event for this reason. The fallback was the same mistake in the other direction: it created a calendar carrying neither a member nor an organisation, and every calendar query filters on both — so the event would have been written, reported as created, and been invisible for good. Both paths now go through **************** which is the same calendar the member's own calendar page uses. A named calendar is checked against the member's own rather than the account's, so one organisation's callback can no longer land on another organisation's calendar.