A CA7 SLA is configured for a job that runs Tuesday through Saturday. The SLA date condition is set to a triggering job that runs Monday night through Friday night. However, the SLA job does not run until the next morning. The SLA has an end time condition with a morning deadline time. However, iDash does not seem to consider that the SLA job is running the morning after the triggering job. Therefore, it is generating "Missed" alerts on Mondays when the SLA job does not run.
When the SLA's date condition is set to a triggering job, the days on which the triggering job runs will be the days selected as the run days for the SLA. iDash does not adjust the SLA run days if the SLA job actually runs the next day. Instead, you must account for this scenario when setting the deadline in the SLA's end time condition.
For an SLA end time condition, the deadline can be a value from 00:00 to 71:59. This allows you to create an SLA where the deadline can be up to 3 days after the triggering job starts. If the deadline is for the same day as the triggering job's scheduled start, you would set the deadline anywhere from 00:00-23:59, as long as it is after the start time for the triggering job. However, if the deadline needs to be for the next day, you would enter anything from 24:00 to 71:59, where 24:00 represents midnight of the day after the triggering job's scheduled start. For example...
SLA date condition is set to a triggering job
Triggering job runs at 10pm Mon - Fri
SLA job normally runs at 5am Tue - Sat.
SLA end deadline needs to be 8am Tue - Sat.
For this scenario, you would set the deadline to 32:00 (24:00 + 8:00), which equates to 8am the morning after the triggering job runs.