It isn’t 100% clear exactly what causes this error, and it should be very rare. Please try again to see if the issue reoccurs. If it does, please see our Support page.
A possible explanation is that the job receives a SIGHUP (hangup signal) mistakenly and the job is terminated. It isn’t clear where the signal might come from. Please see this schedmd bug report for more details.