---
title: Failure node
description: Terminal node that ends an authentication journey in failure, redirecting the user to a failure URL and optionally incrementing the account lockout counter.
component: platform
version: 7.5
page_id: platform:auth-node-ref:failure
canonical_url: https://docs.pingidentity.com/platform/7.5/auth-node-ref/failure.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 &amp; Trees", "Journeys", "Authentication"]
page_aliases: ["auth-node-failure.adoc"]
section_ids:
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  errors: Errors
  examples: Examples
---

# Failure node

The Failure node is a required element indicating the journey ended in failure.

## Availability

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

## Inputs

The failure outcomes of any preceding nodes.

## Dependencies

None.

## Configuration

This node has no configurable properties.

## Outputs

None. The authentication journey ends in failure.

## Outcomes

The authentication journey completes, ending in failure.

AM redirects the user to a [failure URL](https://docs.pingidentity.com/pingam/7.5/am-authentication/redirection-url-precedence.html#failed-url-precedence).

## Errors

The error depends on the Authentication > Settings > Account Lockout > Login Failure Lockout Mode setting for the realm (under Native Consoles > Access Management).

Without the setting enabled, by default, the node returns an error with a message such as the following:

```json
{"code":401,"reason":"Unauthorized","message":"Login failure"}
```

With the setting enabled, the node checks the invalid attempts property of the user profile and does the following:

* Returns a warning message if the number of failed attempts is equal to or greater than the Authentication > Settings > Account Lockout > Warn User After N Failures setting:

  ```json
  {
    "code": 401,
    "reason": "Unauthorized",
    "message": "Warning: You will be locked out after 1 more failure(s).",
    "detail": {
      "failureUrl": ""
    }
  }
  ```

* Increments the failure count in the user profile.

* Returns an error message if the account is `Inactive`:

  ```json
  {
    "code": 401,
    "reason": "Unauthorized",
    "message": "User Locked Out.",
    "detail": {
      "failureUrl": ""
    }
  }
  ```

To troubleshoot an authentication failure, review the steps in the journey to find what caused the failure.

## Examples

All authentication journeys have a Failure node as one of their terminals.
