I bounced BFGMiner, and they went back to normal. Of course, that's the what always resolves an occurrence of the dreaded restart issue.

I just noticed that my miners had both failed work restart testing.

I'm running Titans as well and the only difference I see in our configurations is that I specify a manual diff of 16384, just because that's what I always get when I let the server figure it out. I was seeing your issue too, but bouncing BFGMiner always takes care of it. They've put together a fix t...

Excellent and than-q!

I recently have had issues with my workers becoming "red" in the worker list and get the error this miner is not responding got work restart etc. I did not get that before. ... Over the past weekend, I have been noticing the same thing for my Titans. Bouncing the miner process brings them...

I got those values by seeing what was assigned for me when I let the pool determine the values. Now I specify difficulty explicitly because I feel like it's more efficient than having it determined by a period of sub-optimal mining. (whether that's objectively the case to any meaningful degree, thou...

Sorry, I don't have anywhere near enough data to make a guess one way or the other.

How about a password argument to ID NiceHash rigs? N=yasureyoubetcha or something more succinct?

I suggest that you remove the difficulty setting and see how that works for you. With rented hashing power you can't know the hardware, and so cannot know the optimal difficulty. If that brings no joy, then try setting a restart time. As for what value would be the best, I have no idea, and figuring...

Oh, aye. the "failover only" option is very important. You can find a copy of my config on this thread; it's been working great for me for a long time:
http://forums.prohashing.com/viewtopic.php?f=5&t=524