Depends on how long it took to complete the overdue job. If it finished before the extra copy [sent out 0:00:01 hours after a "No Reply" state occurred], credit would normally be granted. If it was returned after the extra copy reported back, the result is most surely marked "Too Late" when returned and credit is null. When one sees this "consider to abort" line, check in the Result Status WU detail and see how long past and throw the dice on the odds.

To exact what was done: Set the additional buffer to zero several days before departure and the connect to 0.001 days. This causes for new jobs to be fetched just minutes before the previous one finishing. On the day of departure I set the No Work Fetch, to clean out. When the buffer was clean and the system detected there was no activity it went to shleep [hibernation] whilst I was too.

Given all work of last few days was fresh and mostly first to be returned in the quorum, the credit kept coming even on the day of return. As BEST PRACTISE, it is pretty pointless to push the Update button to clear the "Ready To Report" task lines back to the servers, as validation is mostly anyway several days away. It helps the project schedulers to perform in optimum if work fetches and reporting of results are combined. BOINC manages this much better than humans can, really!

Thanks for reading and contributing (a borrowed line )