Session schedules no longer fire twice on multi-replica deployments

On a deployment with more than one server replica, two replicas could both pick up the same due session schedule and send its message twice. Schedules are now claimed atomically, so exactly one replica fires each one. Single-replica deployments were not affected, and no configuration change is needed.

See Session schedules. #3527