---
title: Flow Control node
description: The Flow Control node lets you control the authentication flow by randomly sending traffic down different paths of a journey. This means you can use the node to evaluate changes before rolling out changes to a production environment. For example, configure the node to direct a percentage of requests to a new authentication journey to observe the user experience and check for potential failures.
component: auth-node-ref
version: latest
page_id: auth-node-ref::flow-control
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/flow-control.html
keywords: ["Nodes & Trees", "Journeys", "Authentication"]
superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/flow-control.html
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  callbacks: Callbacks
  outcomes: Outcomes
  errors: Errors
---

# Flow Control node

The Flow Control node lets you control the authentication flow by randomly sending traffic down different paths of a journey. This means you can use the node to evaluate changes before rolling out changes to a production environment. For example, configure the node to direct a percentage of requests to a new authentication journey to observe the user experience and check for potential failures.

## Example

The following sample journey lets an administrator phase in a new authentication path by initially routing a small number of incoming requests to the new login journey for monitoring.

The Flow Control node is configured with the following values:

* Path A Percentage

  `90`

* Path A Name

  `Old Login`

* Path B Name

  `New Login`

The Flow Control node randomly assigns 90% of authentication requests to path A (`Old Login`) and the remaining 10% to path B (`New Login`).

The user follows the allocated path to complete authentication.

![journey control flow](_images/journey-control-flow.png)

## Availability

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

## Inputs

None. This node doesn't read shared state data.

## Dependencies

This node has no dependencies.

## Configuration

| Property          | Usage                                                                                                                                                                                                                                                       |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Path A Percentage | The percentage of requests to send down path A. The remaining percentage follows path B.This value must be an integer. If you're setting this value to an [ESV](https://docs.pingidentity.com/pingoneaic/tenants/esvs.html), the ESV must be of type `int`. |
| Path A Name       | The display name for the outcome of path A.                                                                                                                                                                                                                 |
| Path B Name       | The display name for the outcome of path B.                                                                                                                                                                                                                 |

## Outputs

This node doesn't change the shared state.

## Callbacks

This node doesn't send any callbacks.

## Outcomes

* `Path A Name` *(configured display name)*

* `Path B Name` *(configured display name)*

## Errors

This node doesn't log any error or warning messages of its own.