I'll install the new version afeter 8:00 french time
Hi, if you mean :
If you don't want a task be running at same time after a crash.
Per example a task that run every 5 minutes but don't have to run if the precenet task is still running.
Don't know if it happend to me yet.
But I think it will run twice
Kind of. There are for example, some database jobs you can run, that if you start the job a second time while the first time is still running, it can cause database deadlocks, that in turn freeze the process that called them, and just generally make a mess with scheduling.
So, my question is, if you have any jobs that do *not* have the flag set to not start if an instance is still running, and that have the possibililty that perhaps two instances are running simultaneously, and if that might be something that happens immediately before the crash that you are noticing where the VisualCron server becomes unresponsive.
BTW, my assumption is that the flag in VisualCron refers to the VisualCron job. I think you can separately set a condition based on a process monitor, where you could check if a specific process is or is not running before starting.
Rebeccah