There should be a way to report tasks lost through computer failure or operator errors. These tasks could then be assigned to a new person without waiting for a timeout error. I recently had to install a hard drive which was cloned earlier and had tasks which had already been completed. I turned off receiving new tasks on the cloned drive so that I could reset the old completed tasks on that drive. Somehow, the receive new tasks was turned back and I ended up resetting new tasks which had not been completed along with the old tasks which I had already completed previously. So I am carrying thirty-three tasks which are no longer on my hard drive but are due within three weeks..

---

Earl F. Parrish

The project has an option to resend lost tasks, but due to this being very database intensive, they don't have it on constantly. The option checks between your client's scheduler request and the database if you have all the tasks you should have, and if there are missing ones, you get them resent.

---

just wanted to add my vote for an easier way to recover lost tasks. I'm following a procedure someone posted and have recovered some of my lost ones, but not all of them.

you could restrict it to a low load time on the server or by user (maybe by how long they have been with the project??) so it doesn't get abused.

I agree with Earl. Computers fail, and sometimes aren't rebuilt. Their incomplete work units potentially tie up the main database for months, whereas they could be re-allocated immediately if able to be individually canceled.