is displayed when capturing has been interrupted due to drift and guiding is waiting for deviation be fall below threshold.
Example:

---

2022-02-28T22:49:32 Capturing 180,000-second  image...
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:31 No pending jobs found. Please add a job to the sequence queue.
[message repeated ca. 2000x]
2022-02-28T22:49:29 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:29 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:29 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:29 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:28 No pending jobs found. Please add a job to the sequence queue.
2022-02-28T22:49:28 Waiting for guide drift below 2 a-s...
2022-02-28T22:49:28 Job requires 180,000-second  images, has 5/60 frames captured and will be processed.
2022-02-28T22:49:28 Warning: in-sequence focusing is selected but autofocus process was not started.
2022-02-28T22:49:28 Guiding deviation 1.675 is now lower than limit value of 2,5 arcsecs, resuming exposure.
2022-02-28T22:49:24 CCD capture suspended
2022-02-28T22:49:24 Guiding deviation 3.275 exceeded limit value of 2,5 arcsecs for 3 consecutive samples, suspending exposure and waiting for guider up to 60,000 seconds.
2022-02-28T22:47:06 Capturing 180,000-second  image...
2022-02-28T22:47:06 Job requires 180,000-second  images, has 5/60 frames captured and will be processed.
2022-02-28T22:47:05 CCD capture aborted
2022-02-28T22:46:56 Capturing 180,000-second  image...
2022-02-28T22:46:48 Dither complete. Resuming in 8 seconds...
2022-02-28T22:46:48 Dithering succeeded.
2022-02-28T22:46:41 Dithering...
2022-02-28T22:46:41 Captured /home/trifid/Light/M66_Light_180_secs_2022-02-28T22-46-40_004.fits
2022-02-28T22:46:40 Received image 5 out of 60.
2022-02-28T22:46:40 Download Time: 1.13 s, New Download Time Estimate: 1.19 s.
2022-02-28T22:43:38 Capturing 180,000-second  image...
2022-02-28T22:43:38 Job requires 180,000-second  images, has 4/60 frames captured and will be processed.
2022-02-28T22:43:37 CCD capture aborted
2022-02-28T22:41:16 Capturing 180,000-second  image...
2022-02-28T22:41:07 Dither complete. Resuming in 8 seconds...
2022-02-28T22:41:07 Dithering succeeded.
2022-02-28T22:41:00 Dithering...
2022-02-28T22:41:00 Captured /home/trifid/Light/M66_Light_180_secs_2022-02-28T22-40-59_004.fits
2022-02-28T22:40:59 Received image 4 out of 60.
2022-02-28T22:40:59 Download Time: 1.22 s, New Download Time Estimate: 1.22 s.
2022-02-28T22:37:57 Capturing 180,000-second  image...
2022-02-28T22:37:57 Job requires 180,000-second  images, has 3/60 frames captured and will be processed.
2022-02-28T22:37:54 CCD capture aborted
2022-02-28T22:36:43 Capturing 180,000-second  image...
2022-02-28T22:36:43 Job requires 180,000-second  images, has 3/60 frames captured and will be processed.
2022-02-28T22:36:41 CCD capture aborted
2022-02-28T22:35:50 Capturing 180,000-second  image...
2022-02-28T22:35:50 Job requires 180,000-second  images, has 3/60 frames captured and will be processed.
2022-02-28T22:35:49 CCD capture aborted
2022-02-28T22:35:20 Capturing 180,000-second  image...
2022-02-28T22:35:20 Job requires 180,000-second  images, has 3/60 frames captured and will be processed.
2022-02-28T22:31:25 CCD capture aborted
2022-02-28T22:30:17 Capturing 180,000-second  image...
2022-02-28T22:30:08 Dither complete. Resuming in 8 seconds...
2022-02-28T22:30:08 Dithering succeeded.
2022-02-28T22:29:58 Dithering...
2022-02-28T22:29:58 Captured /home/trifid/Light/M66_Light_180_secs_2022-02-28T22-29-57_003.fits
2022-02-28T22:29:57 Received image 3 out of 60.
2022-02-28T22:29:57 Download Time: 1.21 s, New Download Time Estimate: 1.21 s.
2022-02-28T22:26:55 Capturing 180,000-second  image...
2022-02-28T22:26:47 Dither complete. Resuming in 8 seconds...
2022-02-28T22:26:47 Dithering succeeded.
2022-02-28T22:26:41 Dithering...
2022-02-28T22:26:41 Captured /home/trifid/Light/M66_Light_180_secs_2022-02-28T22-26-40_002.fits
2022-02-28T22:26:40 Received image 2 out of 60.
2022-02-28T22:23:38 Capturing 180,000-second  image...
2022-02-28T22:23:29 Dither complete. Resuming in 8 seconds...
2022-02-28T22:23:29 Dithering succeeded.
2022-02-28T22:23:21 Dithering...
2022-02-28T22:23:21 Captured /home/trifid/Light/M66_Light_180_secs_2022-02-28T22-23-20_001.fits
2022-02-28T22:23:20 Received image 1 out of 60.
2022-02-28T22:20:18 Capturing 180,000-second  image...
2022-02-28T22:20:15 Waiting for guide drift below 2 a-s...
2022-02-28T22:20:15 Job requires 180,000-second  images, has 0/60 frames captured and will be processed.
2022-02-28T22:15:50 Cooler is on
2022-02-28T22:15:49 Cooler is on

This now happens to me every night that I have more than one job CCD image queue. If I have one job, it works fine. If I set up more than one, as when I do R,G,B filter changes, it fails like yours does. And when it does, it skips over jobs. Very annoying. I'm glad it's not just me.

Thanks for confirming the issue, Peter!

I regularly set
"Abort if guiding deviation >" to 2.50 arcsecs" and
"Only start of guide deviation <1.00 arcsecs"

When guide deviation is too high

1. the capture is aborted
2. Ekos is waiting for guide deviation to fall below the 1 arcsecs threshold.
3. During this time the error messages flood the display and the Expose: line shows "Wait for guide".
4. Once guide deviation falls below the threshold, the flooding stops and
5. the next capture is initiated.

In my case this happened in a one-job queue.

Yes, mine does the same. Happened again just now, with one job in the queue. But if I have more than one job stacked up, it skips over jobs until it reaches the last one, and the starts that one. It means I am unable to queue up jobs like before, and have to do one job at a time.

 

 

I cant figure out why this is happening.  Last night it continued to plague my imaging sequence. 
Since no one else has this issue (other than the two of us it seems), I wish I could figure out why this happens to our set up?
I am using the latest Mac OSX version. 

I don't think it's just us two as I believe others just didn't notice the issue yet. I'm running Linux Kubuntu 20.04 systems, very different from your Mac setup. Given the type of issue I would be surprised to find the problem sitting anywhere other than in Kstars itself. If I remember correctly you're running a high end observatory whereas I'm using a Losmandy G-11 and ASI cameras which doesn't hint towards a hardware/driver related issue IMO. Ah, just noticed your footer. So we both share the ASI cams in our setups. Hmm....

Yeah, the Yeah, the problem was crazy tonight, with over 40 of these floods.  Not a peep from anyone about why this is happening.  Weird.  

 

 

Happened to me too! And I found that it just wasted time instead of taking picture! The work was done (exposition taken and downloaded) but no files have been written! 29 out of 59 taken!

It's been happening every night for a month, with all Mac versions of KStars since 3.5.7.
The latest 3.5.8 no better. I wish someone could address it.
I am still unable to shoot with multiple filters because of this issue.

I just asked about this, and there is somebody working on it Please stay tuned.

Thanks Rob. Will there be an announcement when this critical bug is fixed?

Does this bug only effect two people? It's so significant (can't run a sequence) that I am surprised no one else is complaining about it? If it's just two of three of us, what can be causing it on our Mac setups? We're using the latest build, but this only started after 3.5.7.