After canceling the above prompt, the error
appears but (!) together with the notification
When looking at the database again, it seems (!) to have stopped (is not active anymore) but if I start the database again, it becomes visible that the database had actually never stopped since the changes (in this case the noticing of the APOC plugin installation) are not taken into account. In my example, I am not able to call any APOC procedure. I always need to STOP and START the DB for my changes to work.
Some easy-to-recreate examples on how to test it / get to the above problem:
1. Create a new database. Start the database. Install the APOC plugin. Now use the round arrow () next to the Stop button to restart the database.
2. Create a new database. Start the database. Go to the settings. Change anything in the settings. Click "Apply" and "Restart Now".
I also noticed that if you get a "crash" when wanting to restart a db, you will get a problem starting any OTHER database than the one you wanted to restart. The only db you can then actually start normally (without getting the conflict prompt) is the one that you originally wanted to restart which seems to be stopped but actually isn't. Confusing.