Manually stopped services on worker redeployments do not restart post-deployment

[tazlin]

I noted that if the deployment succeeds but the service was previously manually stopped, the service will not restart following a successful deployment, despite the step text indicating that it has.

Either:

• Change the text to reflect that the server might not be starting
• Ensure that the service is started regardless if it is a new deployment or not, or if it was manually stopped.

[db0]

you mean the step Ensure AI Worker service is started. That should start a stopped service. Are you sure the service was the same name and user?

[tazlin]

it was a different user, which should still be a supported scenario IMO

[db0]

No this is not possible. The service exists in userspace so each service is hidden from other users. It should not be a typical scenario to deploy the worker under two different users. And atypical scenarios should be handled manually (i.e. stop the service on the normal user while testing)