Monitoring tasks over midnight is causing all SLOs attached to the object to trigger for violation. The following scenario is useful as an example for the described behavior:
1) A job is executed at 11:30pm.
2) This job will normally run until 12:30, under normal conditions.
3) An SLO is defined to notify in the event of a late running execution, set to trigger a violation at 12:45.
4) Another SLO is defined for monitoring the job, set to notify in the event of extremely long running exeuctions, at 1:00am.
5) The job finishes at 12:50am.
6) Both SLOs are triggered for violation.
7) This behavior is not noticed when the job execution does not span midnight.
Any - this is functionality related to the Automation Engine.
This is currently a functional limitation of SLOs.