Woah! Does this kill the SchedulerThread entirely?! That’s both neat and would maybe explain a long standing “Zombie Worker” problem where it’ll happily stay alive but never dequeue anything ever again.
I actually just reported a bug where if you set a job property to “None” it could crash during an equality check in job.JobProperties (a property which programmers should never need to see). It basically dies within Deadline.Jobs.Job.Equals().
I’m going to throw this on that ticket.
Last time this was reported it went quiet so thanks for not only figuring it out by reported on it! I broke things by setting job.ExtraInfo0 = None but I do not recommend that at all. 