The Client cancels the active computation and spawns a new one by calling NotifyActiveComputeInvalidated(). This does not immediately terminate the computation, it waits for a delay of .CancelActiveOpDelaySeconds for this active compute to finish. This both (1) allows for partial updates to appear at UI levels if the compute is fast enough and (2) avoids constantly respawning new computes as the user (for example) drags a slider parameter.