I found the issue that was causing the problem. The schedulers deleted an operation from the job. Even though the operation was removed it was not “All the way deleted” if you will. I ended up deleting the ghost operation and I was able to release the job.
I’ve been noticing these oddities ever since we patched to 10.1.600.26. I now have a job that has a part number as an Operation and they can’t delete the operation because Epicor immediately put labor on the newly created operation. Just weird!