Task Completion Timer Does Not Reset When Tasks Are Queued

[TheeeKraken]

What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)

Chrome 91 on windows 10

What is the problem?

When multiple tasks are queued for processing, the completion timer does not reset as the various tasks complete, so it is more of a node in use timer than per task- timer.

What should be the expected behavior?

The time elapsed timer noted for each task should recorded the time taken for the specific task, then be reset to zero before moving onto the next task so that it can start its count accurately.

How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? Please include multiple screenshots of the problem! If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)

I have been able to reproduce this problem, whenever I have 3 or more tasks all uploaded and cued for local processing. it does not appear to be data set dependent, but one of the the sets I used can be found at, https://testhub.dronedb.app/r/bigbob39/g9gabxnuhj5jlre3 also is a screenshot of the issue below. it did not take 27 hrs for a single dataset, but it was running all day for all of the datasets that I was processing.

[pierotofy]

I think the current logic starts the timer the moment the task is queued. We should probably change it.