Maybe unrelated to your question, or not. This happened to us in 2022 and we scrapped WM until now we are forced to use it. A thought I had now that I didn't think of in 2022 was to change the name of the WM controller slightly from the TCC controller and the disappearing job/lockup went away. ie Jobname (old TCC) / job-name for the new WM controller. I'm thinking what no one knew back then was that a WM publish would eat a TCC publish instead of update it because the controllers were the same name.
Now, there are a whole host of other issues we are running into with WM being "smarter" than TCC and finding issues for the machines that weren't there before when creating and publishing.
Can we have Site-Vision back?
------------------------------
Tim Todd
------------------------------