If you experience this issue again with the latest version of AbleSet, could you send me a log package so I can take a closer look at what might be causing this?
You can create one by opening AbleSet’s status window, clicking on the settings icon on the top left, and then clicking on “Create Log Package”. To send it to me, you can use my support inbox.
I’ve seen this behavior before on large projects, but I thought I fixed this in AbleSet 2.5.3.