Policy timers

You can configure a policy to run after a specified amount of time.

The timers that are configured for policies are evaluated every day at 3:00 am. If an asset enters a state with a policy configured to run after a certain amount of time, and then the asset leaves that state before the specified amount of time elapses, the policy is canceled.

The timer starts when an asset enters a state. The timer is not reset when an asset is modified.

After the specified amount of time elapses and the policy runs, the timer is reset and begins counting down again. For example, if the timer is set to one week, then the policy runs once a week while the asset remains in the state that is configured with the timer.

When an asset enters a state, or when a policy runs, the next time that the policy will be run is computed by adding the specified number of days, weeks, or years to the current date. The policy is then set to run after midnight of the computed date. Midnight is considered to be the first second of the day.

If an asset enters a state at 11:59 pm on August 1 and the policy timer is configured for one day, the policy will run after midnight on August 2. If the asset entered the state at 12:01 am on August 1 and the policy timer is configured for one day, the policy will also run after midnight on August 2. The policy timer is evaluated by counting the absolute date, not by counting 24 hours. In other words, the days are added to the current date, and not by multiplying the number of specified days by 24 hours and then adding the result to the current time of day. A policy can run in less than 24 hours from the time an asset enters a state, depending on the time of day that the asset enters the state, because the date changed, even though 24 hours did not elapse.

Feedback