How can we help you today? How can we help you today?

Job Did Not Start - Reason: Previous run hasn't finished.

Would it be possible to get some granularity on the Alert configuration for this error?

I know I can disable it for a given job, but that's not what I want to do.

Instead, I would like to be able to disable the alert for (a) given reason(s) - for either all jobs or for a given job.

There are jobs where I expect that they will regularly still be running on the next schedule, so I don't want an alert, but there will be other jobs where if the job is running on the next schedule, this is a big problem - so I do wan the alert.

However, for those jobs where running on next schedule is a expected scenario, I still want to be notified if they don't run for another reason - occasionally we have DC issues where the account used to run the job can't be authenticated, so the job doesn't start - this is an alert I'd like to see.

What are the reasons that response tracks for a job not starting as scheduled - and can the alert filtering choose some but not all?
Bernard Sheppard
0

Comments

1 comment

Sort by
  • priyasinha
    Hi Bernard,

    Very valid point! Regarding more granularity of configuration, we will not be able to do it for the v 1.0 but I have included it in the feature list for the future version.

    SQL Response specifically tracks the following reasons for 'Job did not start' incident.
    1. No target servers defined
    2. Previous run hasn't finished yet
    3. SQL Server agent is not running

    Otherwise we say 'Reasons unknown'.

    We do raise 'Job Failure' incident if the account running the job doesn't have permission. You can view the information regarding the account cannot be validated at 'Returned information for step' under the 'Job step details' section.

    Regards,
    Priya
    priyasinha
    0

Add comment

Please sign in to leave a comment.