CAL_ATT_DROP
Calendar attendee dropped — no resolvable contact
A caller of `/calendar/add-event` (public API or BFF) tried to attach an attendee that could not be tied to a real contact — either no e-mail / member link / customerId was provided, or the supplied identity resolved to the organisation's anonymous shell contact (`anonymous@brj.cz`). The attendee was dropped instead of being persisted; if kept, its reminder e-mails would silently short-circuit as `to-anonymous` undeliverable with no visible cause. Fix the upstream caller to supply a real recipient identity.
What this code means
A caller of `/calendar/add-event` (public API or BFF) tried to attach an attendee that could not be tied to a real contact — either no e-mail / member link / customerId was provided, or the supplied identity resolved to the organisation's anonymous shell contact (`anonymous@brj.cz`). The attendee was dropped instead of being persisted; if kept, its reminder e-mails would silently short-circuit as `to-anonymous` undeliverable with no visible cause. Fix the upstream caller to supply a real recipient identity.
Where you will see it
- In the subject line of technical-notification e-mails — for example
[CAL_ATT_DROP] [calHealthcheck] … - As a badge in the admin log viewer at
/log, where you can filter and drill into individual entries. - In the
core__system_logtable, stored against the code id fromcore__system_log_code.