We had a situation recently where someone issued retest command repeatedly which lead to the old jobs being canceled and replaced by new ones. We should either find a way to configure this that it's not possible - ideally only rerun those that are not already running. Or we should update the retest message with a warning that old jobs are being replaced by the command.