Currently, it is possible that the run state will be set to state RunStates.WARNING even though it was previously already set to RunStates.ERROR. However, an error state should always trump a warning state, which may be treated differently by downstream applications.
Therefore, it is necessary to ensure that the state has not been already changed from RunStates.OKAY before setting a warning state.
Currently, it is possible that the run state will be set to state
RunStates.WARNINGeven though it was previously already set toRunStates.ERROR. However, an error state should always trump a warning state, which may be treated differently by downstream applications.Therefore, it is necessary to ensure that the state has not been already changed from
RunStates.OKAYbefore setting a warning state.