Scheduled Task If Agent is Down Question
What happens to a scheduled task if an agent is down at the time the task is supposed to run? Will it run the next time the agent comes up or will it not run until the next time it is scheduled to run. Which would miss an interval of the job running?
I hope you’re having a great day,
Regarding your questions “What happens to a scheduled task if an agent is down at the time the task is supposed to run? ” and “Will it run the next time the agent comes up or will it not run until the next time it is scheduled to run. Which would miss an interval of the job running?”
If the agent is down, it does not collect any information because the communication between OMW and the node is broken, it depends of the schedule job in the policy but if the agent is down, it does not collect anything due that the agent is the way to communicate and collect information.
Any questions or doubts please let me know
Is it possible to ask for an enhancement request that would include some kind of configuration variable that could detect this and run the scheduled job once the agent comes back online?
Assuming for a moment, the schedule runs at midnight, when the agent was down for whatever reason. The agent is then restarted at 9am - would you want that schedule to work at 9am? What happens if the agent is down for a week, should the scheduled action run 7 times?
You can log enhancement requests via SSO or talk to your support representative.
That is why I am asking if configuration variables could be used to only turn this functionality on when needed and somekind of setting to only run once if down for more than one run instance etc.
I can't find anything which looks appropriate. Please contact your local HPE Software Support team and log an ER, OR log one directly in SSO.
The closest is which are not appropriate in this case is:
On Windows systems, processes started for scheduled actions from the action agent may hang. The action agent was designed to wait until the process finishes. Therefore more and more processes were started and were then blocked.
Defines the timeout period that is used to check whether an old process is killed or the new one not started.
As I could see your requirement and some comments above, in case you want to raise an enhancement request, it is not easy to implement. In some scenario, your request becomes quite complex and the more clear requirement is, the more possibility this ER can be implemented.
Minh Nguyen | SW Technical Support Engineer.
Operations Manager i and Operations Manager
Hewlett-Packard (SSO Portal)
If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.