This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I have a workflow that runs a simple powershell script that moves, renames, and deletes some files at the end of a workflow. It works without error when I manually run the workflow, but when I schedule it (I have designer with desktop automation) to run at night when the computer is locked, I get an error. I have attached a screenshot of my Run Command tool and workflow results.
Has anyone come across this before? It's probably a Powershell problem.
So I made the change in the advanced settings, but it did not work overnight.
When I came in this morning my computer no longer saw it self as a Controller. The service was frozen in a 'Stopping' state. So I changed the service to use my ID as well and rebooted my machine. The scheduler picked back up and ran the job after that.