If you restart the server while you run a job in Optimizely, the job will remain in running state for ever and it won't stop or finish or start anymore.
the only solution to fix this issue is to find your job in tblScheduledItem table and set IsRunning to false.
Looks like there was a fix for this issue released in EPiServer.CMS.Core 12.5.1: https://world.optimizely.com/support/bug-list/bug/CMS-22374
Pretty sure the problem have reoccured if the old release ever fixed it, running 12.9.2 and the jobs still gets stuck if you end the session before they're done.
Can you stop it with "Stop" button in job details page?
I'm using EpiServer.CMS.Core 12.13.1, when click Stop in UI, the job still running, keep writing log, this fix https://world.optimizely.com/support/bug-list/bug/CMS-22374 not actual work, just allow you to restart the job.
We are encountering the same on EpiServer.CMS.Core 12.14
I am trying to understand the issue, I am assuming we are in a DXP environment using app services rather than a physical server. I also presume that you have implemented scheduled job 'stop' correctly (you'd be surprised).
If that is the case then yes, more than likely this will occur as the context / instance the job was running in is lost.
You can ask Optimizely to decicate an instance for you to handle scheduled jobs, therefore if you do need to restart the app service, this should not impact the instance running the scheduled jobs (or at least I hope that is what Optimizely has configured it to do).
I think though there is something I am missing around why you need to restart the app service? Generally restarting an app service should be considered carefully.
It should be fixed with 12.9. bug CMS-24019
@Benjamin - could you press Stop?