I just got a resend of an AP, if the work has timed out I usually get the message that it has "timed out" and of course if the other host finishes it and it validates before I report the wk unit it gets "stuck".
I just got a resend with this message

Not started by deadline - canceled

which implies to me there is no chance of it getting reported before I process it.
Can anybody expound on what is happening? Is this a new refinement and if so when was it implemented?

---

Not running AP tasks at the moment.

But compare with PrimeGrid, where some tasks may be long.

I have PPS Sieve Jade there.

A given or certain task is being sent to a user because the work unit possibly was not being validated.

Perhaps a user received such a task in June, it was delivered or returned back in July and next me, as the second, or maybe third user on the task, was issued, or received the task in August.

Perhaps it takes a month to complete such a task.

That is it. Validity of a given or certain tasks versus the time it takes to process the same task.

Like certain people that may be on your mind, not everything comes cheap, or may be run overnight.

I guess there may be a difference between MB tasks and AP tasks, CUDA or not.

For the moment I am not able to see the difference, though.

The "Not started by deadline" message has been around for a while - I've had them and they are a pain. Once that message arrives, even if you run and report you probably won't get any credit for it :-(

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I've been seeing that message on MB tasks for maybe 6 months. Always on my wingmates, not on my own Tasks. (Only time I've had Tasks time-out is when a cruncher died.)

The few times I've looked at it, seemed to have operated within 12 hours before deadline would have been reached.

---

Donald
Infernal Optimist / Submariner, retired