Did this happen for a patch motion correction job?
If this error occurred on AWS parallelcluster, this might be a question for an AWS forum. Afair, when I encountered this same error, I hypothesized that parallelcluster configuration was still in progress, restarted CryoSPARC, cloned the job and re-submitted. The job then started properly.
I am still curious about the actual cause of this error.
In your slurm submission script, are you using “sh” or “bash”? AWS ParallelCluster does not setup the correct paths to the slurm commands unless you are using bash. So in your cluster_info.json, you should have for example: