Result name                  Status Sent time           Due / Return time   CPUtime/Elapsed Claimed/Granted
SCC1_0004074_MyoD1-A_16525_0 Error  2023-04-26 11:26:45 2023-05-02 11:26:56       -/-          31.7/0

What you see there, is the result of not turning in a task in time.
Your device didn't start that task before its deadline (Due time).
It has been 6 days since you were offered to start - and finish - that task.

Somebody else, called a wingman, also received (a copy of) the task and they finished it in time:

Result name                  Status Sent time           Due / Return time   CPUtime/Elapsed Claimed/Granted
SCC1_0004074_MyoD1-A_16525_1 Valid  2023-04-26 11:26:54 2023-04-28 05:01:53    2.01/2.01       71.5/70.5

Since your task, with its name ending in "_0", didn't finish, another copy (with a taskname ending in "_2") went out to a new wingman:

Result name                  Status Sent time           Due / Return time   CPUtime/Elapsed Claimed/Granted
SCC1_0004074_MyoD1-A_16525_2 Valid  2023-05-02 18:35:52 2023-05-03 13:07:58    2.55/2.65       69.5/70.5

As you can see, they've already finished their task, too.

Adri
PS Thanks for adding the URL of the workunit, else it would have been anybody's guess what'd happened.

Adri has given a neat demonstration of what happened, but it's worth noting that the client doesn't generate a "proper" error message for this situation because it returns a specific result code to the server and expects the server to recognize and report it! Some BOINC projects flag this error as "Not Started by Deadline" on their results pages. WGC, unfortunately, does not[1]!

As a rule of thumb, if you see a result report that only has the client version data in it, it was Not Started by Deadline...

Cheers - Al.

[1] WCG originally wasn't a BOINC-based project, so there are several places where the behaviour is different - another one is the lack of a Server Status page :-)

Ralf - for information:

Unless WCG have changed something in the last day or two I can tell you that whilst WCG correctly uses No Reply (or, later, Too Late) for tasks that are "not returned in time" it reports "Not Started by Deadline" tasks as Error, which I would argue is an error in itself!

And, of course, if a delayed task gets Server Aborted that gets flagged up properly so this was not one of those :-)

The result reporting/flagging disparities between WCG and other BOINC projects can be quite irritating, but it was like that in IBM days too...

Cheers - Al.

P.S. I've got lots of WCG wingman result information if you need me to "show my work" :-)