yesterday, one of my machines received several WUs named "CRYPTICSCOUT_pocket_discovery..."
Since an "ADRIA bandit" WU was still in process, the new ones were in waiting position.

This morning, I noticed that all these "Crypticscout" WUs were cancelled by the server at different time during last night.
Why so ?

these seem to be distributed in pairs, but they only need one result. my guess is that they want to ensure they get the results fast. if they get one result and you haven't even started processing yet, there's no point in having you waste computation on a result they already have. so they cancel it. if you would have been in progress, it wouldn't have been cancelled.

---

these seem to be distributed in pairs, but they only need one result. my guess is that they want to ensure they get the results fast. if they get one result and you haven't even started processing yet, there's no point in having you waste computation on a result they already have. so they cancel it. if you would have been in progress, it wouldn't have been cancelled.

That is correct, and I think it would be a good idea doing this on all the WUs, maybe waving it off when they have too many WUs.

these seem to be distributed in pairs, but they only need one result. my guess is that they want to ensure they get the results fast. if they get one result and you haven't even started processing yet, there's no point in having you waste computation on a result they already have. so they cancel it. if you would have been in progress, it wouldn't have been cancelled.

thanks for the explanation, good to know.
So there is no use in having them sit in the queue for too long time.
Had I know this before, I would have interrupted the Adria task and given priority to the Crypticscout task.
Too bad that no one from the team explains this beforehand :-(

these seem to be distributed in pairs, but they only need one result. my guess is that they want to ensure they get the results fast. if they get one result and you haven't even started processing yet, there's no point in having you waste computation on a result they already have. so they cancel it. if you would have been in progress, it wouldn't have been cancelled.

thanks for the explanation, good to know.
So there is no use in having them sit in the queue for too long time.
Had I know this before, I would have interrupted the Adria task and given priority to the Crypticscout task.
Too bad that no one from the team explains this beforehand :-(

I wouldn't worry about it. you don't get more credit per unit time for crypticscout vs adria or anything like that so there's no reason to interrupt an Adria to prioritize CS. and you didn't waste any time on it for no credit since the task never even started on your system. no harm, no foul.

---

I wouldn't worry about it. you don't get more credit per unit time for crypticscout vs adria or anything like that so there's no reason to interrupt an Adria to prioritize CS. and you didn't waste any time on it for no credit since the task never even started on your system. no harm, no foul.

The situation was a different one:
I had 1 Adria running and 3 CS in the queue. So with the current situation that new WUs become availble scarcely, I would have had 3 more to crunch once the Adria got finished. So, Adria got finished, and no other ones left :-(

but they were crunched already by someone else. so why waste the time on it? similarly, it would be the same if you completed first. why should someone else waste the time on it?

unless you want to crunch tasks unnecessarily just to ensure you get more points?

---

but they were crunched already by someone else. so why waste the time on it?

yeah, you are right !