We’ve noticed a build where the “Ran for” time is reported incorrectly. It reported 44 minutes, but the longest sub-job took and 1 hour 27 minutes. Clearly it ran for more than 44…
See this screenshot
Did you restart the job immediately below the highlighted one?
Oh, interesting point. It’s very possible. I don’t know though… It seems weird to overwrite the runtime if you restart one of the jobs but not all of them though.