When you ask to install/upgrade/uninstall an extension, a first job is run to compute a plan of what will need to be done (which dependencies will be installed, backward dependencies uninstalled, etc.) to give a chance to the user to check and accept it before it's applied.

In a very active wiki, you can end up loosing this plan at the end because it's pushed out of the job result cache between the two refreshes of the UI.

The safest to avoid this problem would be to change the current logic to have only one job, with a question in the middle to validate or cancel the plan. It would also speed up the full installation process (because the second job currently have to recompute the plan).