@qitsweauca Caution: We are not sure about the current state of your CryoSPARC instance and therefore unsure about the ultimate effect the following suggestions may have. Please backup your database and ensure there are no legitimate Live sessions running on your CryoSPARC instance if you wish to proceed (at your own risk):
# cryosparcm icli
import datetime
try:
rtp.pause_session('P38', 'S5')
except:
db.workspaces.update_one({'project_uid' : 'P38', 'session_uid' : 'S5'}, { '$set' : {'status' : 'paused'}, '$push' : {'paused_at' : datetime.datetime.utcnow()}})
(see Logs are being flooded - #3 by stephan)
Then, identify and “correct” inconsistent CryoSPARC sessions as described in No jobs showing up after recreating database - #6 by nfrasser.
[Edited 2023-10-11: try rtp.pause_session() first; ensure no running Live sessions]