When we retry the consul handlers, we refetch the value - if it just so happens, that the value changes after one of the handlers has finished successfully, but another is still retrying, the successful one might not be called at all with the most recent value.
a watched value changes, handlers A and B are set to run
A passes on the first try, but B throws an error so it's retried
after 5 retries, the value changes again, so the next call of B will be with the new value
...but A isn't called again at all, ever
Currently, this breaks the set-active system tests