Hi @jpd, this might happen if the job was created before an update. Try creating a new identical job through the job builder (don’t use clone). Then run that instead.
If that doesn’t work I’d recommend a force-reinstall with this command:
Hi @nfrasser, We are having the same issue when running cryosparc 3.2, and we tried to run a force update, however, ran into the same error - when running a patch motion correction, we receive this error:
[CPU: 90.3 MB] Traceback (most recent call last):
File “cryosparc2_worker/cryosparc2_compute/run.py”, line 51, in cryosparc2_compute.run.main
AssertionError: Job signature invalid.