Would it be possible to have the full verbose log of your test? I'll check what is happening. I assumed that the job would repeat because the scheduler considered it was not finished. That behavior is controlled by Remember Job Progress, and there is a potential issue when you don't have a filter wheel in the setup that makes the capture check unable to find the frames. But there the "0/0" is puzzling, it's possible that this strange count is confusing the scheduler. At least it's not preventing you from running captures! I believe running the job until a fixed timestamp should allow you to shut your observatory down properly.

-Eric

Run a test with all simulators devices (CCD guider, telescope, focus and filter) in a local configuration .
Kept "Renember Job Progress" not checked and used three filters.
Still the count is 0/0 and the scheduler tries to restart the job after completion.
Attached the full verbose log of this test (job completion is line 662. Line 1039 is where I manually stopped the job).

Thanks again for helping

EDIT: also run test with different 'Job Completion Conditions'.
'Repeats for 1 run' enters a loop of runs until I manually stop it.
'Repeat until <time>' repeats batches until it reaches the scheduled time and then triggers shutdown, as you said.

Same problem here, I noticed that it does not create a directory, like it did before,
but save image in Kstars/Light and remain in "capturing" ..have to stop manually.
Scheduler is very important.

Thanks.

I just committed a few fixes to GIT, please check or wait for nightly and report back.

Hi knro, I see your change, compiled and tested with simulators. Now photo is saved in just directory, only work remain in "capturing".
Add log and file used as test ( test photo of polaris without align, guide, ecc.. ).

Thanks.

Sorry I didn't understand "Only work remain in capturing"?

Sorry, you are right, my english is horrible.

When he finishes capturing, remains in "capturing", for end have to press stop button.

Add video.

Would it be possible to correct the scheduler?
It is a very important part of Ekos

I expose the problem, but my English is limited.
The problem is: when it finishes capturing the photo, it does not stop (and move on to another if present).
It remains in acquisition and the photo counter always remains at 0.

I plan to check it soon don't worry about it.

Ok just tested with nightly and it worked just fine.. I just found out that the nightly build in the PPA was failing, so I need to fix that as well first.

Thank you for your great work.

P.S.
You have to put new change online? ..I compiled from git now, and problem is still present.

Still present with the same scheduler file you shared with me? weird.. it works just fine here... is "Ignore Job Progress" checked or not in options?