This is arguably solved now, because we no longer delete the service immediately. However, I'm treating this bug as the representative for the next step. In that step, the service will get an alert in the inspector when services die, destroying will try to resolve units in error, dying units will be shown in their own bar, and dying units in error (the destroy hook or whatever it is) will get their own bar. We're hoping this gives better visibility into what's going on and what to do about it, while adding just enough automation of the standard path.
This is arguably solved now, because we no longer delete the service immediately. However, I'm treating this bug as the representative for the next step. In that step, the service will get an alert in the inspector when services die, destroying will try to resolve units in error, dying units will be shown in their own bar, and dying units in error (the destroy hook or whatever it is) will get their own bar. We're hoping this gives better visibility into what's going on and what to do about it, while adding just enough automation of the standard path.