Hello. I ran across an odd behavior in the latest Kstars/Ekos version 3.6.2 stable (which I recently upgraded to) on Ubuntu 20.04. I was running a capture job of 30 x 300 second subs on the Flaming Star nebula. After completing 17 of the 30 images, the logs show dithering, then guiding resumes, then them mount performs a meridian flip, which was expected since the mount was just past the meridian. That's when the job appears to abort. Below are the log entries:
****begin log snip****
2023-01-26T21:20:31.072 CST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 300.000-second L-Ultimate image..."
[2023-01-26T21:20:31.122 CST INFO ][ org.kde.kstars.indi] - ZWO CCD ASI183MC Pro : "[INFO] Taking a 300 seconds frame... "
[2023-01-26T21:21:42.358 CST WARN ][ default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-01-26T21:25:32.027 CST INFO ][ org.kde.kstars.indi] - ZWO CCD ASI183MC Pro : "[INFO] Exposure done, downloading image... "
[2023-01-26T21:25:32.047 CST INFO ][ org.kde.kstars.indi] - ZWO CCD ASI183MC Pro : "[INFO] Download complete. "
[2023-01-26T21:25:32.917 CST INFO ][ org.kde.kstars.indi] - "FITS" file saved to "/home/enigma/Light/L-Ultimate/IC_405_Light_L-Ultimate_300_secs_2023-01-26T21-25-32_017.fits"
[2023-01-26T21:25:33.301 CST INFO ][ org.kde.kstars.ekos.capture] - "Download Time: 1.20 s, New Download Time Estimate: 1.24 s."
[2023-01-26T21:25:33.576 CST INFO ][ org.kde.kstars.ekos.capture] - "Received image 17 out of 30."
[2023-01-26T21:25:34.575 CST INFO ][ org.kde.kstars.ekos.capture] - "Captured /home/enigma/Light/L-Ultimate/IC_405_Light_L-Ultimate_300_secs_2023-01-26T21-25-32_017.fits"
[2023-01-26T21:25:34.581 CST INFO ][ org.kde.kstars.ekos.capture] - Dithering...
[2023-01-26T21:25:34.581 CST INFO ][ org.kde.kstars.ekos.capture] - "Dithering..."
[2023-01-26T21:25:34.581 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Dithering started."
[2023-01-26T21:25:34.585 CST INFO ][ org.kde.kstars.ekos.guide] - "Dithering in progress."
[2023-01-26T21:25:34.922 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Dithering started."
[2023-01-26T21:25:35.867 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Guiding resumed."
[2023-01-26T21:25:35.873 CST INFO ][ org.kde.kstars.ekos.guide] - "Autoguiding started."
[2023-01-26T21:25:39.420 CST INFO ][ org.kde.kstars.ekos.capture] - Dithering succeeded, capture state "Dithering"
[2023-01-26T21:25:39.420 CST INFO ][ org.kde.kstars.ekos.capture] - "Dithering succeeded."
[2023-01-26T21:25:39.421 CST INFO ][ org.kde.kstars.ekos.capture] - "Dither complete. Resuming in 10 seconds..."
[2023-01-26T21:25:39.425 CST INFO ][ org.kde.kstars.ekos.guide] - "Dithering completed successfully."
[2023-01-26T21:25:39.429 CST INFO ][ org.kde.kstars.ekos.guide] - "Guiding resumed."
[2023-01-26T21:25:39.510 CST WARN ][ default] - QImage::scaled: Image is a null image
[2023-01-26T21:25:49.611 CST INFO ][ org.kde.kstars.ekos.capture] - "Capturing 300.000-second L-Ultimate image..."
[2023-01-26T21:25:49.706 CST INFO ][ org.kde.kstars.indi] - ZWO CCD ASI183MC Pro : "[INFO] Taking a 300 seconds frame... "
[2023-01-26T21:29:41.365 CST INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2023-01-26T21:29:41.366 CST INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2023-01-26T21:29:41.367 CST INFO ][ org.kde.kstars.ekos.guide] - "Mount is slewing. Aborting guide..."
[2023-01-26T21:29:41.375 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Calibration is cleared"
[2023-01-26T21:29:41.385 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Guiding Stopped."
[2023-01-26T21:29:41.386 CST INFO ][ org.kde.kstars.ekos.capture] - "Autoguiding stopped. Aborting..."
[2023-01-26T21:29:41.390 CST INFO ][ org.kde.kstars.ekos.capture] - "CCD capture aborted"
[2023-01-26T21:29:41.397 CST INFO ][ org.kde.kstars.ekos.guide] - "Autoguiding aborted."
[2023-01-26T21:29:41.860 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Guiding started."
[2023-01-26T21:29:41.864 CST INFO ][ org.kde.kstars.ekos.guide] - "Autoguiding started."
[2023-01-26T21:29:42.237 CST INFO ][ org.kde.kstars.ekos.guide] - "PHD2: Guiding Stopped."
[2023-01-26T21:29:42.241 CST INFO ][ org.kde.kstars.ekos.guide] - "Autoguiding aborted."
[2023-01-26T21:29:42.432 CST WARN ][ default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-01-26T21:30:02.357 CST WARN ][ default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-01-26T21:30:22.364 CST WARN ][ default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-01-26T21:30:23.442 CST WARN ][ default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-01-26T21:30:23.922 CST INFO ][ org.kde.kstars.indi] - iOptron GEM45 : "[INFO] Slew complete, tracking... "
****end log snip****

I was not running this job via the Scheduler. I manually slewed, aligned, focused, and began autoguiding (using PHD2 service through Ekos interface), and then started the capture from the capture tab.
This worked fine in the prior version I had (3.5.x? cant recall exact version). Am I missing a new setting somewhere in v3.6.2, or is this potentially a bug?
Thanks,
Peter

I had a similar error, and there the reason was that the meridian flip was not initiated by EKOS, but by the mount itself. What are your MF limits, both on the mount and in EKOS?

Ah Ha! Thank you Peter.
I discovered that in the new version 3.6.2, in the Mount control tab, Flip if HA > was set to 5 deg. The mount itself is configured for automatic meridian flip at 2 degrees. Thus the mount itself initiated the flip instead of Ekos.
The 5 degree setting in the Mount tab must be a new default. In the older 3.5.x version, I had it set to a time based setting (Flip if HA > .04 Hours) that was less than the time it would take for the mount to travel 2 degrees past meridian. In a way this seems easier to manage (no more calculating how many clock minutes in a RA degree, etc..

Clear Skies.