Looks like somehow the flight number got changed from 104 to 114, and the MCT exception is flight number specific. It's unintentional I'm sure .... guessing it should be back to normal with the next schedule load, either with an additional MCT exception added or a flight number change.