Hi @hickschad8,
Is this happening for just P3 or all projects? Something similar was encountered in this thread: V4.0 Validation lock error
On startup of a CryoSPARC instance, lock files should be automatically created for known project folders that don’t have them. If other projects on your instance are working, this may be an indication that there was an issue writing a lock file to the project directory of P3. This error should be visible somewhere in your command_core.log file.
To further test, can try calling the API function for generating the lock files:
cryosparcm cli "take_over_projects()"
This function should write lock files to all projects in the instance, and any errors encountered will be visible in the command_core.log file.