On other sciences, after for instance 9 or 10 errors for a task, very common on android, and one or more in pending validation or pending verification state, the distribution is stopped, any in those pending states will convert to 'too late', retroactively . Usually these get credit same as claimed and be added to my contributions.

More elegant would be to create a new class, something like 'irreconcilable'. At any rate, these get removed pretty fast from the result status page, the question of how many copies were distributed for that task already 'too late'.

The 'server aborted' show will only happen when the client has communicated back and reciprocated the home base request, to do so. Else it will remain showing 'in progress'. Not sure if the task was started if it still gets server aborted i.e. an enforcing. In case of the server determining it's a bad build, would go along. If just superfluous to requirement because an older 'no reply' still came in, think it's left to run to the end.