Notification API ghost subscriptions on reconnect

The socket is dropping without a close frame, but the channel stays ACTIVE in the backend. I’ve tried nuking everything with DELETE /api/v2/notifications/channels/{channelId}/subscriptions before the new handshake, but the subscriptions keep leaking. It’s ABSOLUTELY ridiculous that the state doesn’t clear.

{
 "status": "400",
 "message": "The request could not be processed",
 "code": "Bad Request",
 "details": "Channel already has maximum number of subscriptions"
}
1 Like