Looks like if your capture sequence is writing XISF files, the scheduler "remember progress" algorithm won't recognize the downloaded images. Must be only counting FITS, and doesn't recognize XISF files as images. I see the following in the log after every stored XISF capture:
"Job 'LBN473' 20x300\" Sii sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Light/Sii'."
"Job 'LBN473' 20x300\" Sii requires a dither procedure."
"Job 'LBN473' 20x300\" Ha sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Light/Ha'."
"Job 'LBN473' 20x300\" Ha requires a dither procedure."
"Job 'LBN473' 20x300\" Oiii sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Light/Oiii'."
"Job 'LBN473' 20x300\" Oiii requires a dither procedure."
"Job 'LBN473' 20x30\" Sii sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Flat/Sii'."
"Job 'LBN473' 20x30\" Sii captures calibration frames."
"Job 'LBN473' 20x2\" Ha sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Flat/Ha'."
"Job 'LBN473' 20x2\" Ha captures calibration frames."
"Job 'LBN473' 20x15\" Oiii sees 0 captures in output folder '/home/airbourn/Pictures/LBN473/Flat/Oiii'."
"Job 'LBN473' 20x15\" Oiii captures calibration frames."
"Job 'LBN473' estimated to take 05h 31m 01s to complete."
Hmmm - upon further investigation, it appears that the Scheduler doesn't catch FITS files in the directories either. What am I missing? Is there a file name length limit or something? The paths are correct.
This becomes an issue when the Scheduler restarts a job after an abort. It doesn't recognize anything already done and starts all over. I have the "Remember Progress" box checked.