Force non-incremental execution after cache load failure Previously when handling a failed load we did clean the outputs of the work, but ended up allowing incremental execution nevertheless. This is now fixed.
Notify about changing outputs early We can do this as soon as we've decided that the outputs will change, i.e. when we already know that we can't entirely skip executing the work. This removes some duplicate code, too.