How 'Clear Alarm(s) for Last Run Result' will work on Scheduled Tasks?
Usually Scheduled Task's Last Run Result Alarm retains and affects the monitor health until it runs on the next time.In some cases,the next run time will be more longer based on the scheduled task.So that there is an option called 'Clear Alarm(s) for Last Run Result' to manually remove the alarm if they needed.
Clear Alarm(s) for Last Run Result will clear the current Last Run Result alarm of the selected task and it won't re-alert until it runs next time
New to ADSelfService Plus?
Related Articles
Why don't I see the custom messages & replaceable tags given in an action in the alarm escalation notification ?
Alarm escalation provides the option for escalation if any alarm has not been attended for a given time period to an email address(s) or mobile number(s) or if a specific program was executed. The notification template & work flow logic used in the ...
Scheduled Tasks Monitoring - Access is denied Error
If you are to connecting to a remote Windows Vista computer from a Windows Vista, you need to allow the Remote Scheduled Tasks Management firewall exception on the remote computer. To allow this exception: Click Start, Control Panel, Security. Allow ...
Alarm Configuration for JOBs under AS400 Monitor in Applications Manager
Alerts can be configured for the STATUS attribute of individual jobs in IBM i(Previously AS400) Monitor. In the Jobs Tab, you will find an option called Add Job(s) to Monitor. You can click and add the corresponding jobs which you want to monitor. ...
How to generate alarm history for more than 30 days
In Applications Manager, the alarm history for a monitor's attribute is preserved for a period of 30 days. This encompasses various metrics such as health, availability, and performance (individual attributes such as CPU Utilization, Memory ...
Critical\Warning alarm was raised, but action wasn't triggered
1.) Ensure that actions have been associated for the attribute that generated the alarm. For example, if the CPU utilisation of the server exceeded the permissible levels and generated the alarm, navigate to Monitor page-> Configure Alarm and ...