Occasionally, under circumstances I have not been able to reproduce, the Hoist command stops working and I am unable to hoist any part of the binder. Generally I keep Scrivener open; when this happens, I close and restart, and the problem is fixed. This has been happening for the last year or so, through updates. Not a major inconvenience, and I have not been able to link it to anything I do (other than keeping Scrivener open for days without restarting), but I wondered if anyone else had seen this bug.
There are a variety of reasons why you might not want to leave Scrivener open for days, as there are a number of housekeeping tasks that only run when it is closed.
In particular, Scrivener’s automatic backups typically run on close. Check the settings in the Scrivener → Settings → Backup pane to make sure they match how you prefer to work.
I have not seen that happen, nor recall any reports of it. Is the problem that the command is disabled in the menu, or that it is available but when you use it nothing happens?
Given that it only seems to happen after a while, and that a restart clears it, my guess is that something else is happening (perhaps even over night) that is throwing a silent error that in turn is breaking other things like this. Something I would recommend doing is going into the General: Warnings settings pane, and enabling internal error alters for a while. This will make those silent warnings much less silent. You’ll get a bit pop-up as soon as something goes wrong, with some debugging info for us, and a button to quit so as to avoid further problems.
What I would do however, instead of immediately quitting, is trying to hoist. If after you get an alert it doesn’t work, well… we may not know the original problem, that depends on what triggers it, but at least you know why that isn’t working when it should.