3D Flex Train and Reconstruction falsely fail due to 'no heartbeat'

Application
1

Hello,

I have noticed during large 3D Flex Train and Reconstruction jobs (hundreds of thousands of particles) that they will report ‘failed’ with the ‘Job is unresponsive - no heartbeat received in 60 seconds’ error, but if you check the log they are actually still running just fine; ie. iterations are continuing to increase. Then, once the job finishes it will properly report ‘job complete’. I am running Cryosparc 4.1.2.

I think this is just a superficial issue, but it would be nice to have 3D Flex jobs report their state properly.

Thank you,
-Alex

2

Update: This might be an issue with our institution’s cryosparc servers. I am getting the same behavior on some non-uniform refinement jobs.