I'm having a problem with the scheduler. It ran a job once. When I reset the job and run it again, it does everything up to the capture part, launches the capture, and says it is complete and exits. Logfile snippet:
I believe I figured this out. The fact that the job ran once but not again was an indicator.
Renaming the file from the first job allowed the job to start and capture. The software must be erring on the side of not overwriting previous images.
Feature request - set up defaults such that a unique identifier is always appended to an image. TS would do, but it defaults to off. It's pretty easy to overlook - I did it several times at this point. Oops.