My issue is different in that no changes to the job would fix it, but creating a brand new job with the same VMs and the same settings is now working without the error. At least for the first few I am addressing. Will be interesting if the other jobs throwing this error also get fixed just by creating new jobs while many other jobs never had this problem after the 12.1 update.
thanks for chipping in, everything helps
thanks for chipping in, everything helps
Statistics: Posted by William Bohn — Jan 05, 2024 9:00 pm
