A FAAH on UD has been stuck now for several hours in the 33% range (probably 1 our CPU time), oscillating up and down.....a known event. What i have not figured out is, when the red dotted curve should appear....most of the times is shows during the return and retry, but this one has none. It's probably very simple, like it has not build a reference expected yet or something to that effect. It's now 2 hours CPU time into the WU, where the first 30% odd progressed rapidly, faster than a normal toothy FAAH.

This one is another example where it spend 45 minutes CPU time build up, snoozing, then closing for a boot and resuming at 25 minutes clock, where it previously had progressed to several hours clock......resuming, where the initial docking setup completed. Clients need a warning in the home [^] screen of UD agent for this behavior !!!!! We've seen many a comment that it would not consolidate the position for restart even at 50%!