This morning I noticed two tasks with 0 runtime, Valid, and granted credits > 400.
One of them was ARP1_0026737_090_0, workunit 818600061.

Further investigation - when clicking on its status (Valid) - shows the Results log: the task has been running for about 12 hours (first checkpoint 11:09:39, last checkpoint 22:07:27).

However, the API response backing that result shows 0.00341 hours of CPUtime, which equals to about 12.276 seconds (and 0.00349 hours of elapsed time, which equals to 12.564 seconds).

There is an accurate log of the job:

$ grep ARP1_0026737_090_0 ~boinc/job_log_www.worldcommunitygrid.org.txt 
1632254958 ue 37914.391201 ct 44197.420000 fe 214491871892342 nm ARP1_0026737_090_0 et 45177.688204 es 0

It tells us that the elapsed time (et) was 45177.688204 seconds, which is 45177.688204 / 3600 = 12.54935783 hours.

So CPUtime and elapsed time should be about 12.50 (hours), not 0.00.
(This is obviously a problem.)






EDIT: (The following just demonstrates some text conversion from the workunit page. )
(Note: Got wcgformat working again, too, finally. )
Using wcgformat, after mouse-selecting the two lines of results from the workunit and feeding this to wcgformat -o, it shows as:

Result name        OS type      Status      Sent time       Due / Return time  CPUtime/Elapsed Claimed/Granted
ARP1_0026737_090_0 Linux Fedora Valid  2021-09-21 06:45:47 2021-09-29 06:45:47       0/0           828/672.2
ARP1_0026737_090_1 Linux Debian Valid  2021-09-21 07:10:11 2021-09-29 07:10:11   34.17/34.36     516.4/672.2