Scheduled jobs that crashed the app still appear to be Running when it's not

Vote:
 

I ran the "Search & Navigation Content Indexing Job" which caused the web app to use too much memory. That caused the web app to be restarted, but there is no information about that in the job. It looks green and Running, but it does nothing after restart. It also does not help that the Status is mostly just " - " for this long running job, so you don't know if it is in the beginning or the end of indexing, or if it's even doing anything. I've seen that for other jobs as well; you can see status updates, but every now and then it goes blank " - ".

#310091
Edited, Oct 05, 2023 9:17
Vote:
 
  1. This should be addressed in later version of CMS Core - i.e. a stopped scheduled job should appear as such (not running )
  2. we have a story in backlog to add start up time and run time of a scheduled job. it might not be released very soon, but hopefully soon enough 
#310092
Edited, Oct 05, 2023 10:23
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.