Unfortunately this is a known bug after some updates on group scheduling. I haven’t found a way to reproduce it yet and from source code after a quick look I didn’t find what could cause this.
As I’m going to implement some more changes in the near future for group scheduling, I’ll take a deeper and I’ll try to locate the issue.
Until then feel free to remove these observations or report them to me here or in personal message in order to remove them.