My pipeline script has

try{
			
			jobToRun = build job: jobName, parameters: jobParameters
			jobStatus = jobToRun.result
			print "Job: ${jobName} completed, result was ${jobToRun.result}"
           
	}
	catch (Exception e){
			println "DEBUG: error message is: " + e.message
}

Which used to work about a month ago. Updated plugins and core, and now e.message == NULL

e == org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

This is when $jobName != SUCCESS. A bit annoying that a build call throws an exception in the first place

Changing the severity, as I can use propagate which solves all the issues I was trying to solve by catching the exception in the first place.