---
title: Account Active Decision node
description: Checks whether a user account is both active and unlocked, routing the journey along True or False outcome paths in PingAM.
component: platform
version: 7.5
page_id: platform:auth-node-ref:account-active-decision
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/account-active-decision.html
llms_txt: https://docs.pingidentity.com/platform/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["Nodes & Trees", "Journeys", "Accounts"]
page_aliases: ["auth-node-account-active-decision.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  examples: Examples
---

# Account Active Decision node

The **Account Active Decision** node determines whether the current account is both active and unlocked, and lets the journey make a decision, based on that check.

An account is considered locked under these conditions:

* The status is inactive.

* The status is active and a duration lockout is set on the account.

An account is considered unlocked under this condition:

* The status is active and no duration lockout is set on the account.

The node determines whether the account has been locked through both persistent (physical) lockout and duration lockout. Learn more in [Account lockout for trees](https://docs.pingidentity.com/pingam/7.5/am-authentication/about-authentication-trees.html#account-lockout-trees).

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

The node reads the `username` from the shared state. Implement the following node before this node in the journey:

* [Username Collector node](am-only/username-collector.html) (standalone AM)

* [Platform Username node](platform-username.html) (Ping Identity Platform deployment)

## Dependencies

This node has no dependencies.

## Configuration

This node has no configurable properties.

## Outputs

This node doesn't write anything to the shared state.

## Outcomes

* `True`

  The journey follows this outcome path if the account is assessed to be `active` and `unlocked`.

* `False`

  The journey follows this outcome path if the account is assessed to be `inactive` or `locked`.

## Errors

If the node cannot read the identity of the account, it throws the following exception:

`Failed to get the identity object`

## Examples

In this simple login journey, authentication fails if the account is assessed to be `inactive` or `locked`.

![Account active Decision node in a simple login journey](_images/account-active-decision-node.png)

This example uses the following nodes:

* The [Page node](page.html) prompts the user to input their username and password:

  * The [Platform Username node](platform-username.html) collects the username and stores it in the shared state.

  * The [Platform Password node](platform-password.html) collects the password and stores it in the shared state.

* The [Data Store Decision node](data-store-decision.html) uses the username and password to determine whether the account exists.

* The **Account Active Decision** node determines whether the account is active and unlocked.

* If the account is active and unlocked, the [Increment Login Count node](increment-login-count.html) increments the login count and authentication succeeds.

* If the account is inactive or locked, the authentication fails.