I am heading on vacation and set all my projects to no new tasks. They were finishing before WUProp would finish, so WUProp would be the last task to finish and end and report. There was about 10 minutes left on it when the other tasks finished and reported.
The task did not stop at the 1 hour mark. It kept running and running for over 6 hours, until I had to abort it before shutting down. So the time in the task is lost.
So there needs to be logic in it, if there are known workload in a task and then no workload, the task should end as normal on the 1 hour mark and report the less than 1 hour of work it had obtained.

---

My movie https://vimeo.com/manage/videos/502242

Yes, noticed it too, had to abort the last task here too.

---

.

More than a year later issue still not fixed.

---

.

So there needs to be logic in it, if there are known workload in a task and then no workload, the task should end as normal on the 1 hour mark and report the less than 1 hour of work it had obtained.

Actually it could end instantly when the computer runs out of other work and the credits could be adjusted to the time it has run (just like they are adjusted when BOINC is running with disabled network for some time and the task runs longer).

Than, if the user didn't suspend work fetch from WUProp, the next task could have a limit of 24-72 hours (or simply the deadline if possible) if running without other work.

---

.

So there needs to be logic in it, if there are known workload in a task and then no workload, the task should end as normal on the 1 hour mark and report the less than 1 hour of work it had obtained.

Actually it could end instantly when the computer runs out of other work and the credits could be adjusted to the time it has run (just like they are adjusted when BOINC is running with disabled network for some time and the task runs longer).

Than, if the user didn't suspend work fetch from WUProp, the next task could have a limit of 24-72 hours (or simply the deadline if possible) if running without other work.

I've noticed it as well so now I run short gpu tasks until the wuprop task gets sent back then I stop the gpu tasks and shut down the pc.

I've noticed it as well so now I run short gpu tasks until the wuprop task gets sent back then I stop the gpu tasks and shut down the pc.

I simply set WUProp to NNT more than one hour before the tasks finish. Not much to care about IMHO, the results page, which is the only "scientific" result of this project is half broken since years now (and I'm not sure it was ever fully functional) and all results are deleted after 72 hours instead of keeping them for those who want to check something. This is insane. On Grafana for example I can go back in history nearly two years, why not on WUProp?

---

.

On Grafana for example I can go back in history nearly two years,...

Just thanking you for that website. New to me.