Personally, I wouldn't expect so...

Actually, knreed noted that it could happen as gap in the controls, all the more reason to select at least 1 generally available science. Personally wish the rule would not kick in until a core threatens to go idle... no idea how to have that work with the many variations of client versions on the grid.

The fix / workaround if you absolutely do not want a specific science for personal or technical reasons: Deselect that ''if''option and run with a reasonable buffer. 1 day pretty much bridges any outage... 2 days if you fear that the Earth will stand still on a day.

edit: Included replied quote for clarity.

For the Linux platform it has a rather big share, considering that on WCG maybe 5 percent is Linux... 5% of 337 Years yesterday is 17 and of that 5 years going to CEP2.

Of course if the system specs don't meet it should not be send anyhow if that were a concern.

Expecting that a portion will switch back to Windows when that port is available in production. Me, never again for dedicated crunching. Simply much more throughput / efficiency... HCC half the time, C4CW 60% faster, other sciences from small to materially faster. Certainly not slower.

Opt-Out to include it not being send when the ''If'' kicks in... who knows somewhere in the future. knreed has mentioned that something would be implemented that would exclude sciences on which a specific device always / mostly fails. No point in sending those regularly, maybe now and then one to test if the problem has disappeared.