Hi YYZ,
Making sure I understand the behavior. The jobs that are showing in the “completed” status in the job controller, are preventing other jobs from running on the next schedule?
What is the error on the job that is unable to run on the next schedule, or is it going into a queued status?
Hi Jason
They stay as a queued job
@YYZ , I’m not aware of this issue. I would definitely get a case created (and share the incident number here).
Thanks!!
Hey @YYZ , following up on this one.
Did you get it resolved? I’m not seeing a case in your name.
Thanks!
Hi Mike
I had not raised a ticket (due to time, pressure etc, and ‘manually’ managed clearing the processes for a few days.
Now that you’ve pinged me - I ‘realise’ the issue has gone.
ie. It hasn't occurred for the past 7-10 days.
‘Nothing’ has changed in the system - other than upgrade the CommServe through various MR finally to to 11.38 (related to another commvault Ticket thats been ongoing for a while)
I ‘think’ that coincides with the issues going away.
I appreciate the follow up - It had purged from my mind some how
Out of sight, out of mind I guess
I’ll mark your reply as the answer then!