I picked up a Beta on one of my machines that had the restarting loop problem. The new Beta just finished successfully. It was checkpointing and honoring my Use At Most 70% of CPU throttle setting. So the fix worked great on my machine.

Karen

Edit: mistakenly thought this was a FAHV beta to test a fix for the looping problem.

Beta14 v6.21 is an old beta app reference I think, just the production version from before the project suspend, in Beta-dress.

My Linux got received 2 copies and tested throttle as that bug showed it's ugly face again, but thought it was only reported for the currently 'new' FAHV(?). Set it to 90% which is as ugly as 70%, running 9 seconds, pause-preempt 1 second [recommend to up the 70% to 75% so it runs 3 seconds, pause 1 instead of run 7 seconds, pause 3 seconds]. Nothing untoward.

P.S., If you need cooling, the function of the throttle, the best setting is 50% [WCG default] which alternates 1 second running, 1 pausing. Just good to not let fans rev up and down.

For laughs, the first Beta validated

BETA_ SN2S_ 4EL6_ 0000000_ 2079_ 1-- 621 Valid 7/23/13 03:56:04 7/23/13 04:53:17 0.93 81.4 / 50.1
BETA_ SN2S_ 4EL6_ 0000000_ 2079_ 0-- 621 Valid 7/23/13 02:07:54 7/23/13 06:20:46 0.62 18.8 / 50.1 < moi

Something borked, a 50% slower device 'claiming' > 4 times more. Yes, the OAB at work... not Casino Royale, but Casino WCG

Reading the news Beta test for Schistoma - A new project was my first thought, but no it was just that Keith let slip so of the pen.
Anyway, I only got 1 resend to verify which of 2 results of pending wingmen is valid
Tested throttling and suspend/resume with and without LAIM selected - no issues.