So we're seeing an issue now every time after system patching where we have a job or two that error out with the error logging into runtime user.
We have restarted the server multiple times and the server-side Tidal service on the server even more times and tried all sorts of things with the Tidal-side scheduler to get these to work, and only when the Tidal-side connector was disabled and re-enabled (with the server-side Tidal service stopped and started in between) did things start working as intended. Whats even weirder is error ocurs when jobs were kicking off as scheduled, but they could be re-run manually successfully. Ther are other jobs on the problematic server that runs as scheduled with no issues.
Is this a bug. Our agent for the machine the job runs on is 3.1.0.13. The machine is server 2012
