Managing a job without the target language produces a fatal error

Yes, we can add a check here, but the snippet is this:

if (!$job->getTargetLangcode() || $job->getTargetLangcode() == LanguageInterface::LANGCODE_NOT_SPECIFIED) {
      $job->target_language = key($available['target_language']);
      $target = '?';
    }
    else {
      $target = $job->getTargetLanguage()->getName();
    }

So it only goes into the if if the target langcode is that is not empty and not UND. So unless I'm missing something, this can only happen if you create a job with a target language and then delete that language. Which I suppose is a valid scenario, especially if you're trying out things.

Confirmed and reproduced, this does fix that, but not sure what we're supposed to do with these jobs then.