My DSFL tasks are normally running for about 14-15 hours.

And if you are still worried do a few extrapolations of the elapsed time** at specific percentages (e.g. 10, 20, 25, 33, 50...) to see if it is gone for your usual run time or really for a very abnormal one.

And last, report again with the name of this WU when it is complete if the CPU time has been abnormally high for this device.

** Ignore estimated times until they come back to normal.

I too am getting excessive run time. For some tasks my percentages don't seem to change even after several hours have passed. I have aborted several tasks that have been running for 40 hours or so, and the estimated time left keeps getting longer. I've not had this sort of thing happen with any other projects. When my computer completes a task for Drug Search for Leishmaniasis it takes around 7 1/2 hours. I'm guessing that the tasks should take about the same length of time, and when I get up to 20, 30 or 40 hours, I fugures something is wrong. I abort the task so my computer can work on something that will be useful.

Thanks for your suggestions Lawrence. I haven't tried re-booting. I'll try that next time and see what happens.

As a diagnostic, the program could check successive checkpoints to make sure all is well, and if it's not alert the user or abort the task.

Thanks Again.

Dave