This was a UI/websocket display bug. At no point was the matching engine actually in a crossed state.