(imported topic written by nls82591)
Can anyone tell me why Actions don’t repeat, even though the relevance is "name of operating system contains “Sun” AND exists file “/opt/BESClient/bin/” " and the execution screen is set to “reapply this action when relevant, waiting 1 hour between reapplications” and with no end date in the constraints.
(imported comment written by SystemAdmin)
Did the action fail (in which case you need to check the “on failure, retry” option), or do you have a “limit to x reapplications” setting checked?
(imported comment written by nls82591)
It succeeded the first time it ran. All it does is execute a file which creates some temp files, it works once but never repeats. This is how it’s set up:
Messages
No user interface will be shown before running this action.
No message will be shown while running this action.
Users
This action will run independently of user presence.
User interface will be shown to all users.
Execution
This action starts 04/01/2011 13:59:01 client local time.
This action will never expire.
It will run between 06:00:00 and 17:59:00 client local time, only on Monday, Tuesday, Wednesday, Thursday, and Friday.
If the action becomes relevant after it has successfully executed, the action will be periodically reapplied an unlimited number of times, waiting 1 hour between reapplications.
If the action fails, it will not be retried.
Post-Action
No operations will occur after the action completes.
(imported comment written by SystemAdmin)
One thing to note is that the “wait 1 hour between reapplications” really means "wait
at least
one hour between reapplications".
This is because the client constantly evaluates all its content in a big loop, one item at a time. How long it takes to go through this loop depends on how much content you have, and how they are written (some expressions are slower than others).
If for example it took an hour to evaluate all your content on an endpoint (most deployments are much faster than this), and you had an hour wait between reevaluations, then it might take up to 2 hours to evaluate this content (because the agent skipped it on its first loop, since it hadn’t reached its reapplication time, and had to wait to get to it in the next evaluation loop).
-Zak