I encounter database busy a lot. But I found that repeated requests are bad, because they bog down the server.
There is no other way to tell if coreprotect is working on your command.
Hence, this request:

1. Show some coreprotect status as it is working on your command, if possible (e.g. % complete).
2. Do not allow user to add another rollback/restore command if it is already working on one, but allow Abort, Undo, or Inspect
3. Add an Abort command (similar to undo, except it can halt the ongoing operation, and just undo everything that has been done so far)
4. At least allow people to Abort if they are using the #preview qualifier. It should not have changed anything, and should have the same effect as /co cancel.

As it seems you're referencing rollbacks/restores, rollbacks/restores already show the progress.

Previews can already be cancelled with /co cancel.

Rollbacks should typically only take a couple seconds. If rollbacks/restores are taking a significant amount of time, or your database is repeatedly stating it's busy, you make have some other issue going on, such as extremely slow IO speeds.

Please ensure you're using Paper, as well as the latest version of CoreProtect.

Thank you for your response!

Leaving this open as a suggestion for the following:

Allow inspecting while rollback/restore is in progress

This should now be possible without causing issues on SQLite setups.