I want to have logic in my lifecycle state calculation that returns inactive if the user is already in the inactive lifecycle state. The idea being that inactive users should not automatically change lifecycle state, so this would be a safeguard such that if the lifecycle state calculations change or the identity attributes that calculate lifecycle state change, then the user remains in the inactive state until manual intervention is taken to move them out.
Has anyone done something like this before? Is this possible? If so, please explain what steps you took to put in place this safeguard.