Job Does Not Get Triggered by <Jobname> and Triggerinig Job Does Not Exist

Products

• iDash Workload Automation

Issue/Introduction

Observed the following error message while editing an SLA in iDash:

Job does not get triggered by <jobname>.  Click ACTION Edit and select valid Date Scheduling option.

or

Triggerinig job does not exist. Choose a valid job.

Trigger SchID does not exist.  Choose a valid SchID.

I'm trying to understand what caused this and how and why this happens. 

Environment

CA Workload Automation IDASH 12.0

Resolution

It looks like the SLA was set up at a time where it was triggered to run by other jobs.

Now, it is no longer triggered to run by other jobs. The warning messages are to tell users that the SLA definition is not valid and should be updated.