OK. A bit more testing.
'abort autoguide on failure' unchecked
Now, both guiding and capture are resumed BUT not if the guiding fails during a dither.
Is there any chance of getting both guiding and capture restarted if guiding fails during the dither and during the exposure?
In the capture sequence, do you have set a delay? If I set a delay and have the "Abort Autoguide on failure" option set, then guiding starts, but capturing not. Instead, it shows "Waiting..." on the Capture tab.
TSA-120 + FSQ-85 + GSO 150/750 | Avalon Linear + M-zero | Moravian G2-8300 + ASI 1600mm pro + ASI 294mc pro | KStars/INDI on Raspberry Pi 4 with Raspbian 10
Hm, as a workaround you could set the delay to 0 and do not select the "Abort Autoguide on failure".
Alternatively, you could try to use my fix directly. If you know how to compile from sources, simply add my kstars fork as new remote and checkout the branch "scheduler_restart_guiding_dithering_errors". This works like this:
Ah, ok. Is there a new fix today?
It's clear here in Spain tonight so I'm out imaging (hoping we don't lose it on a dither!).
But of course, tomorrow, I'll work out the git stuff and build your branch.
Meanwhile, could you post if the fix (if there is a new one) makes it to master?