We've not yet arrived at/announced a resolution to this problem. Yes, it was working for a while, but that was not a permanent solution. Last word I heard from tech is that it turns out to be a core VB issue that can't be fixed at this time without compromising overall site performance. So, no resolution is projected as forthcoming. Tech may be able to do the occasional restart, but it won't be meaningful until they announce that they have it resolved. We just don't want to unreasonably raise expectations on this. Sorry about that.