Hi David,
Setting track_jobs_in_database = True should not be required, recovery is
supposed to work either way.
Does Galaxy lose all jobs, or just the ones that completed while Galaxy was
restarting? Can you provide the output from the Galaxy log that shows an
attempt to recover a job and all
What are the configuration steps required for allowing a local Galaxy
installation to be restarted without affecting currently running jobs? I have
Galaxy using DRMAA to submit jobs onto a backend cluster. I thought that
enable_job_recovery = True should allow this, but in a few tests I have
