Thanks, I understand that, but what if this computeris also "no reply, a third one is sent... and when does that stop ?

Well to be honest I think it highly unlikely you would get four or more no replys in a row on a workunit. After the second no reply the system sends it to a computer it records as being very fast and very prompt and accurate in sending workunits back completed. Usually these will run at high priority by BOINC when the computer they are received on sees them.

Now if there is a bad workunit that errors out several times then the system in charge of the project puts a halt to the workunit and aborts it from the system so the techs can figure out what is wrong with the workunit.

There was a bad batch of workunits in the DSFL project that caused it to be halted and the workunit batch to be redone for example.

The current functionality in the 'Results Status' webpage pivots on the cruncher; that is, a list of a cruncher's WUs that are of a status-type. For example, if the filter is set to Result Status: in-progress, a list is returned of all WUs of the cruncher that are in-progress.

There is another functionality which is not currently a feature of the 'Results Status' webpage: a dataset that pivots on the wingMachine (and not on the cruncherMachine). Here, what a cruncher is interested to know is how many wingWUs (and not a cruncher's WUs) are of a certain status. If this wingMachine-pivot functionality is available along with the cruncherMachine-pivot functionality, and both can be used at the same time, for your case, set the cruncherMachine-pivot to "Valid" and next set the wingMachine-pivot to "No Reply". That should return a list of your WUs which are "Valid", with the wingWUs of a status of "No Reply".

As long as a WU is a wingWU, you should get a list of all WUs (with at least one wingWU with a No-Reply status) that was associated (in a quorum) with your valid WU. Now if only the wingMachine-pivot functionality is available...
;