I’m also using an Astroberry and get the same messages when the guiding goes out of range. However it does seem to recover and continue with the job when the guiding improves. I’m only running a single job at a time as still a beginner.
Yes, the sequence will restart - but not when you have multiple tasks in the sequence. It skips over the other tasks, making sequencing completely unusable.
I use an autofocuser that moves the guidestar a full arc minute or more with every focus, and while EKOS can recover and bring it back to center - that process always causes a guiding abort - which then triggers this bug. That ruins the whole sequence. This is a major problem, making remote overnight sequences impossible. I wish someone would fix this.
So it's at least 4 users who experienced the issue and I bet many others stumbled on the same issue but didn't notice. I didn't either until I checked my logfiles.