Timing and Verifying Lifecycle State Changes

Key Takeaways

  • Changes to identity data during aggregation or provisioning can initiate event-based identity processing.

  • Scheduled processing evaluates eligible identities in the configured tenant time zone. Check eligibility and queue delay.

  • Use nextProcessing for a planned per-identity evaluation with a future ISO 8601 value at least an hour after update.

  • A manual lifecycle state can persist while the source value stays unchanged. Check the effective state and target results separately.

Last updated: November 2026

Choose the trigger that matches the requirement

Identity processing evaluates identity mappings, manager relationships, role membership, and selected lifecycle actions. An aggregation can supply changed source data, but the trigger for processing can also be elapsed time or a configuration change. Decide whether the business needs a response to new account data, a routine reevaluation, a planned individual date, or an operator action. Processing that starts a target operation does not itself validate its success.

Cause or requirementProcessing option to evaluate
Aggregation or provisioning changes the identityEvent-based processing for the modified identity
An eligible identity’s existing hire date needs reevaluation as time passesScheduled processing and the applicable periodic calculation
Evaluate after a specific known future timeMap Next Processing Date, nextProcessing, for the identity profile
A mapping or access-model definition changedPreview as appropriate and use Apply Changes or the supported targeted processing option
An administrator must explicitly select a state as an exceptionSet Lifecycle State for that identity and verify the manual result

The documented scheduled windows are 8:00 a.m. and 8:00 p.m. in the tenant’s configured time zone. Morning eligibility involves Active and Inactive (short-term) identities with an account on a source configured for attribute synchronization. Evening eligibility includes those identity states if roles are implemented. In a tenant without roles, the profile must have an attribute marked for periodic refresh for that evening case. Check the actual identity state and configuration. The windows are queue times, so other work can delay a start. Do not assume a transition happened at exactly a named boundary because a schedule exists.

For example, a worker has a hire date in the profile and unchanged HR data overnight. If the identity is Active and has no account on a source configured for attribute synchronization, the morning window is insufficient for this case. The evening window can evaluate this identity if the tenant has roles. In a tenant without roles, check whether the profile requires periodic evaluation. If the business must evaluate earlier, plan a separate documented trigger.

Set a per-identity processing time

SailPoint’s time-based processing uses nextProcessing. Map a future date and time in ISO 8601 format, using a transform if needed. It must be at least one hour after the attribute is updated in the tenant. Suppose an approved design processes a worker on 2027-04-11 at 15:00 UTC. The attribute updates that day at 13:30 UTC and the mapping produces 2027-04-11T15:00:00Z. The time is ninety minutes after the update and meets the lead-time rule. A value at 14:00 UTC has only a thirty-minute lead and does not meet it. Run the test early enough to populate the field and check the expected result. Time-based processing adds an evaluation opportunity alongside applicable scheduled processing. It does not certify that a later connector request will complete by a fixed deadline.

Apply a configuration change to the intended population

Preview a changed lifecycle mapping with representative identities. Apply Changes from the identity profile processes the associated identities. From roles, access profiles, or applications, it applies to identities in Active or Inactive (short-term) identity states. To process a pilot identity, find it in the Identities list and use Actions > Process Identity. This recalculates configured values and is distinct from manually choosing a lifecycle state. Use the Active Jobs list on the Monitor page while a processing job is running.

Distinguish data fixes from manual state actions

An administrator can explicitly select a lifecycle state. The interface shows the result as Manual and initiates the corresponding lifecycle provisioning. SailPoint documents that the manual setting can hold while the underlying source value remains unchanged. When that source value changes, the state returns to an automatic value. Plan how an exception should end instead of assuming that the next ordinary run always clears the manual setting.

If a worker remains in the wrong state, inspect the profile’s mapped value, its case and whether the destination state is enabled. SailPoint distinguishes an unmapped or null value, a value that is not a defined state, and a case mismatch. Check whether processing was eligible or initiated and then inspect the result independently of the target action. For example, a valid terminated state and failed account disable can coexist. The failed action still needs troubleshooting using its status and target evidence.

See SailPoint’s identity processing modes and times, state assignment and exceptions, and identity state eligibility.

Test Your Knowledge

An identity’s nextProcessing attribute is updated at 13:30 UTC. Which future value meets SailPoint’s minimum lead requirement on the same date?

A

14:00 UTC

B

15:00 UTC

C

13:59 UTC

D

13:30 UTC

Test Your Knowledge

An administrator manually sets a state. The underlying authoritative state value later changes and is evaluated successfully. What result should the engineer expect?

A

The manual state permanently overrides any future source changes

B

The change is ignored unless the source becomes non-authoritative

C

The provisioning result is automatically proven by the source change

D

The lifecycle state can return to Automatic using the changed source value

Sections you finish are checked off in the contents.