One of those days, but express progress time as percent of 18 hours , the coded cut-off, and you may be close. Mine run back to back about 2 to 3 hours for all 16 jobs and the percent to progress ratio is worse. There's so much in the agent time to progress computing guesstimating, trying to cater for so many projects, exceptions and quirks, it's daunting task to get anything consistently proper. In the case of cep2 the programmers could introduce a 'whatever is bigger'. Either the percent to time or the number of completed jobs out of the 16, something along those lines. Given the variable runtime of each job of the 16, try code that.

Saw in the development notes a new parameter is coming that can be added to the app_config in case the progress is considered 'accurate' for an application. Would not know if this would help cep2 or not or for that matter on any wcg application.

Lavaflow... you may be on to something... it makes sense about the "Progress" being the percentage of the 18 hour cut off limit. I was trying to compare "Progress" vs "Remaining" and it appears that they are two different concepts. It would be helpful if the title of the "Progress" were a little more descriptive... something like "Progress to cutoff limit" or something like that. Thanks for that observation... it makes a little more sense now.

CJSL