cases where this goes wrong, as noted in the release logs, this is just a temporary fix, in 2.5 can solve it properly with notifiers.
cases where this goes wrong, as noted in the release logs, this is just a temporary fix, in 2.5 can solve it properly with notifiers.