WU 14809 completed successfully but reassigned

[comixgoddess]

I returned the WU in question successfully on July 31, well before the timeout . Here is the relevant section of my log -

07:58:26:WU00:FS00:Sending unit results: id:00 state:SEND error:NO_ERROR project:14809 run:2387 clone:1 gen:42 core:0xa7 unit:0x0000002d455e42065ec1245d10e082dd
07:58:26:WU00:FS00:Uploading 6.76MiB to 69.94.66.6
07:58:26:WU00:FS00:Connecting to 69.94.66.6:8080
07:58:32:WU00:FS00:Upload 20.35%
07:58:38:WU00:FS00:Upload 46.24%
07:58:44:WU00:FS00:Upload 61.97%
07:58:50:WU00:FS00:Upload 85.09%
07:58:54:WU00:FS00:Upload complete
07:58:54:WU00:FS00:Server responded WORK_ACK (400)
07:58:54:WU00:FS00:Final credit estimate, 4111.00 points

As I had not seen any credit yet, I checked the WU Status page. It's showing that the same WU was reassigned, returned, and credited to another folder on August 2. Did my WU not count? Not sure if this is an oddity with this particular WU or with the server.

[Neil-B]

If the server to which you returned was a CS and the WS didn't know it had returned it might have reissued?

[bruce]

I'm hearing reports of poor back-end communications between some of the CSs and the stats subsystem. I can't guarantee those reports are either valid or invalid.

I'm not sure whether to believe that CS avast1 is successfully syncing with the other servers. Unfortunately if there happens to be a problem there, it's hard to find what happened because you only know it was uploaded successfully and not credited yet.