In my organization, we use rails with Action Cable with Redis, and we faced some infra issues where Redis had to restart. The Rails server continued to work fine, including Active Job with the sidekiq adapter, but Action Cable wasn’t able to repair itself in this situation. The current cable connections did not get disconnected, and the new cable connections still tried to reach to the old redis connection, resulting in a silent failure. Restarting the rails server did the trick, but this isn’t feasible, Action Cable must be able to recover from such cases or at least not fail silently. I propose disconnecting the cables when the redis connection closes and rejecting connections while redis is down. This way at least the client and server can recover if redis is down and reconnects. If this is an welcome feature, helping the reliability of Action Cable, I can implement it.