Lifecycle Events evaluation interval

  • Release version: Australia
  • Updated March 12, 2026
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Lifecycle Events evaluation interval

    ServiceNow’s Lifecycle Events evaluation interval manages how and when timers within lifecycle event workflows trigger activity sets. This mechanism ensures efficient automation by triggering activities either immediately or based on configurable conditions, rather than solely relying on periodic evaluation intervals.

    Show full answer Show less

    Activity Set Triggering Methods

    Activity sets within lifecycle events can be triggered by various methods:

    • Immediately
    • By a date
    • Trigger script (advanced)
    • Conditions based on table fields
    • Combination of different trigger types
    • Other activity sets (which must wait for dependencies to resolve before triggering)

    This flexibility allows customers to tailor lifecycle event automation to their specific processes.

    HR Activity Launcher Flow and Evaluation Interval

    When a lifecycle event case changes to the Ready state, all activity sets pass through the HR Activity Launcher flow. Activities within those sets do not trigger immediately unless conditions are met. If trigger conditions aren't satisfied, the system waits for a Wait to reevaluate Trigger Script timer (default every 4 hours) before rechecking. This default interval is controlled by the snhrle.All activity set closure timer under Lifecycle Event Properties.

    Administrators can reduce this interval to accelerate triggering, but must do so cautiously to avoid excessive event triggers that may cancel ongoing activity sets.

    Condition with Event BR (Demo) Activity Set Alternative

    As an optional, more immediate triggering approach, customers can use the Condition with Event BR (Demo) activity set included in demo data. This method leverages server-side code (business rules, event scripts, scheduled jobs) to fire the checkactivitysettrigger event, which prompts the HR Activity Set Trigger Check workflow to evaluate activity set conditions immediately.

    • Requires activating the Human Resources Scoped App: Lifecycle Events for Enterprise (com.snhrlifecycleent) plugin.
    • Applicable only to activity sets with Condition trigger type, excluding immediate or dependent activity sets.
    • Includes a demo business rule that monitors lifecycle event state changes and triggers the event.
    • Customizable to fit customer-specific workflows and notification needs.

    HR Activity Set Trigger Check Workflow

    This workflow is integrated with the HR Activity Launcher and is responsible for evaluating whether an activity set’s trigger conditions are met when notified by the checkactivitysettrigger event. It does not trigger activities directly but ensures timely re-evaluation outside the default interval.

    Practical Actions for ServiceNow Customers

    • Adjust the snhrle.All activity set closure timer to optimize how often activity sets are re-evaluated, balancing timeliness and system load.
    • Consider implementing the Condition with Event BR (Demo) approach to enable faster activity set triggering through server-side events.
    • Customize business rules and workflows included in the demo set to meet your organizational requirements.
    • Understand that activity sets triggered by other sets require dependency resolution before firing.
    • Review Lifecycle Events trigger configurations to ensure proper automation of activity sets.

    There is a mechanism available to ensure timers within a workflow trigger automatically rather than wait for the evaluation interval to trigger.

    Activity sets can be triggered using different methods based on how you configure it:

    *When an activity set is triggered by other activity sets it must wait for all dependencies to resolve before triggering.

    HR Activity launcher flow

    When a lifecycle event case is changed to the Ready state, all activity sets run through the HR Activity Launcher flow. The activities in each activity set are not triggered at this time. When an activity set is not dependent on other activity sets to trigger activities, the trigger conditions are analyzed.

    If the trigger condition has not been met, it waits for the Wait to reevaluate Trigger Script timer to run (default is every four hours).

    If the trigger condition is met, but after the evaluation interval runs, it has to wait another four hours before the activities set is re-evaluated. This can cause delays in an activity set to trigger.

    The Wait to reevaluate Trigger Script timer uses the sn_hr_le.All activity set closure timer field under Lifecycle Event Properties to determine when to evaluate the activity set. The default value is four hours.

    You can reduce the value in the sn_hr_le.All activity set closure timer field in order to launch the activity set sooner.
    Note:
    Use caution if you decide to change the default value. Frequent updates trigger more events and can cause your lifecycle event activity sets to cancel before it can complete. For more information, see Lifecycle event properties.

    Condition with Event BR (Demo) activity set

    An alternative to using the Evaluation interval field is to use the Condition with Event BR (Demo) activity set that is included with demo data as an example of what you can use. This is an optional solution, but you can create and use server-side code (business rule, event script, scheduled job, etc.) that triggers the check_activity_set_trigger event into the HR Activity Set Trigger Check workflow. Any activity set can be triggered using the check_activity_set_trigger event from the server side with the exception of activity sets that are triggered immediately or only by other activity sets.
    Note:
    To access the Condition with Event BR (Demo) activity set, activate the Human Resources Scoped App: Lifecycle Events for Enterprise (com.sn_hr_lifecycle_ent) plugin. This is an optional method that can be used instead of the values in the Evaluation interval field.
    • The trigger type for the activity set must be set to Condition.
    • The Condition with Event BR (Demo) activity set triggers when the state of primary lifecycle event case moves to Work in progress.
    • The Email - Condition with Event BR (Demo) activity is included with the Condition with Event BR (Demo) activity set.
    • The Condition with Event BR (Demo) activity set contains the HR Activity Launcher workflow. It also contains the Condition with Event BR (Demo) business rule.
      • The Condition with Event BR (Demo) business rule runs after the state of an LE case changes to Work in Progress.
      • It then looks for the workflows that are running for the LE case until it finds the HR Activity Set Trigger Check workflow and broadcasts the check_activity_set_trigger event to that workflow.
    • You can modify the Condition with Event BR (Demo) activity set, Email - Condition with Event BR (Demo) activity, and Condition with Event BR (Demo) business rule to fit your requirements.
      Note:
      For more information, see Lifecycle Events workflows and Business rules.

    HR Activity Set Trigger Check workflow

    The HR Activity Set Trigger Check workflow (see below) was added to the HR Activity Launcher workflow so that any server-side script can notify the workflow to see if the activity set is ready to trigger.
    Note:
    It does not trigger the activity, it evaluates the condition of the activity set.
    • The HR Activity Set Trigger Check workflow is called when an activity set is not dependent on other activity sets.
    • It periodically checks if the trigger condition for an activity set has been met.
    • If the trigger conditions have not been met, it still waits for the evaluation interval to run.
    • If the check_activity_set_trigger event fires, the Activity set trigger conditions are checked immediately.