Sometimes it's sheer luck that there is a maximum of only four wingmen, thinking of the not unlimited time to finish and upload a result and the fact that people are aborting tasks.

This is the story of ARP1_0018335_011… (No, not Ma Baker)


Two copies of ARP1_0018335_011 were distributed on 13-05-2020 at 19:56 (times in UTC).
Only 15 minutes later, wingman _0 abandoned control, so copy _1 was left to my own device.
The WCG server immediately took action and sent out copy _2 (on 13-05-2020 at 20:11).
Unfortunately, the operator of the computer behind copy _2 decided to cancel that task the next day,
that's why it got its status User Aborted on 14-05-2020 at 17:18.
In turn, another wingman was assigned a copy a few minutes later: _3, with seven days to return the result.

Days went by, in the meantime my device reported its result for copy _1 (on 16-05-2020 at 09:34).
Then, nothing happened, so the deadline for copy _3 arrived (21-05-2020 at 17:20) and still no answer from that machine with copy _3.
One option left for the WCG server: to send out the last possible copy (_4) for workunit ARP1_0018335_011.

Things were getting dire as it seemed that there was only one chance left to get a Valid result.
Or was there still a small chance that the result for copy _3 would be reported back to the WCG server?
(The deadline this time was 25-05-2020 at 05:20.)

Again, days went by where nothing seemed to happen and so it was that big day, 25-05-2020 finally, the last chance to meet the deadline.
Of course, we don't want to be kept in suspense any longer, we want to know what happened. Well, I'll tell ya.

Suddenly, half an hour past midnight, the machine with copy _3 returned its result, although more than three days late
(after 10 days and 7 hours) and with a 4 day runtime (96 hours) for that task: but … just in time! (with a few hours left on the clock)
And what's more, only five minutes later, the result for copy _4 was also handed in.
I was almost in cold sweat, did they try to scare me?

Long story short:

Result Name          OS           AVN Status       Sent Time         Due / Return Time CPUh  Claimed/Granted
ARP1_0018335_011_4-- Linux Ubuntu 727 Valid         5/21/20 17:21:55  5/25/20 00:35:06 10.69   511.2/1,223.5
ARP1_0018335_011_3-- Linux        727 Valid         5/14/20 17:20:30  5/25/20 00:30:45 96.88 1,389.8/1,223.5
ARP1_0018335_011_2-- LinuxMint    727 User Aborted  5/13/20 20:11:10  5/14/20 17:18:57  0.00   530.5/0.0
ARP1_0018335_011_1-- Linux Fedora 727 Valid         5/13/20 19:56:17  5/16/20 09:34:26 21.76 1,057.2/1,223.5
ARP1_0018335_011_0-- Linux CentOS  -  Detached      5/13/20 19:56:07  5/13/20 20:11:06  0.00     0.0/0.0

[Generated by wcgformat]

Moral of the story:
Don't abort your ARP1 task , there's plenty of time left for it (as long as you don't let it get out of hand).
(Even if the deadline passes by, you'll still have some time left after the next wingman returns their result. )