Sorry from the log I don't see what the problem could be. However, because I've been hit by that issue yesterday, check that it's not the same CCD that is used for guiding and capturing.
Going through my change list, I'm about to push a commit fixing the issue with repeated job iterations when the scheduler does remember job progress. The test I made this night was involving a sequence on M51, 10x40", repeated 300 times. With the change, the scheduler properly planned for 18 hours of imaging (though estimation of job duration is still completely off), mostly properly counted captures and mostly recovered when aborted/reset or paused/restarted
I also added an interesting change, at least for me right now. Repeated jobs that are not requested to guide will realign the target each time a batch is complete. This allows unguided sessions to both keep the target centered and process a meridian flip when the batch finishes.
However I'm still checking possible regressions...
First, I had issues with my remote solver providing its result properly, but Ekos simply ignoring that and keeping waiting for something. Switching to the online solver did not trigger the symptom, so I used that for this night. My indi remote is still 1.6 though.
Second, as I mentioned earlier, I had the issue where the CCDs of the remote indi server are enumerated in a different order as in a previous run. In my case, this defaulted all CCDs in Ekos to the MGen guider, which doesn't provide usable frames. In my case this is a no-go for the focuser so I could spot the issue, but I wonder what would happen if the CCD was providing a real frame.
Also, because my indiserver got disconnected 20min after starting, I registered a new change to my todo list to use a retry algorithm in that situation, now that in my branch, aborted jobs are verified and eventually rescheduled if not complete.
Sorry if that sounds confusing, I'm progressing very slowly, but very cautiously...
@knro now that kstars requires indi 1.7 to build, should there be a warning when connecting to a 1.6 server? Is that a hard incompatibility or a compile-time requirement?
-Eric