Notify administrators of a channel connection problem

When a connected channel stops working, every user who administers channels is notified once, and stays notified only until the connection recovers.

When this happens: The channel health check or a send failure detects the connection leaving the *Active* state.

Step by step

1
Open the notification and lands on the connection's page in Channel Administration (FR-15) to reauthorize it.
The channel health check (FR-15) finds the WhatsApp connection +373 69 000 111 has moved from *Active* to *Requires Reauthorization* after repeated token failures. EasyCRM checks for an existing open ChannelConnectionProblem notification for this connection; finds none. EasyCRM creates a ChannelConnectionProblem notification, naming the connection and its state, for every user holding EasyCrm.Channels.Manage, and pushes it.

Other paths

Connection recovers and fails again

The connection returns to *Active*, then later degrades again. Because the previous notification's dedup key cleared on recovery, a new ChannelConnectionProblem notification fires for the new incident.

If something goes wrong

Connection already has an open notification

At step 2 an unrecovered ChannelConnectionProblem notification already exists for the connection (e.g. A second health-check failure before anyone acted). No duplicate notification is created.

Good to know

Notifications are deduplicated per connection until it recovers.
Recipients are every holder of EasyCrm.Channels.Manage in the tenant — channel administration is not scoped by conversation visibility. (FR-15, FR-10-017)