i ssh'd in, and it was running fine, so I must have missed it (or you may have reset it).
Just to test, I manually cycled through a few of your manual profiles and was unable to reproduce

Could have just been a fluke? I'll do some failover tests my manually blocking out a pool with iptables on my machine just to make sure there isn't some new problem, but for now its hard to say what caused the problem you witnessed.
now i can see
I'm looking at screen with logs
not monitor screen
0-$ control 1$ localhost (2*$Log)
so i'm reporting feature not bug

My bad
before ctrl+a switched between control an monitor, now control and log

ctrl a 1
fixed it