---
title: Flow view
source: https://docs.newrelic.com/docs/pathpoint/flow-view
---

> #### 💡 PREVIEW
>
> We're still working on this feature, but we'd love for you to try it out!
>
> This feature is currently provided as part of a preview program pursuant to our [pre-release policies](https://docs.newrelic.com/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).

This page covers the updated version of Pathpoint. For the generally available version, see [Introduction to New Relic Pathpoint](https://docs.newrelic.com/docs/new-relic-solutions/business-observability/intro-pathpoint).

![A screenshot showing the Flow view, including a stage-level KPI.](https://docs.newrelic.com/images/pathpoint-detail-view.webp "Flow view")

The Flow view shows the active health status of a flow, and is designed to make it simple to identify the areas experiencing issues in the journey.

To open the Flow view, click any row of the **Flows** page. See [Flows page](https://docs.newrelic.com/docs/pathpoint/get-started-pathpoint#flows-page) for more.

> #### 💡 NOTE
>
> The Flow view reflects the live health status of your signals, refreshed at the interval set for the flow.

Each Pathpoint flow is divided into:

**KPI bar**

![A screenshot showing the business health with four business metrics.](https://docs.newrelic.com/images/pathpoint-kpi-global.webp "KPI bar")

At the top of the Flow view, the **KPI bar** displays the key business metrics configured for this flow, such as order fulfillment time, cart abandonment, or revenue. These give you immediate context on the business impact of what you're seeing below.

KPIs can also be associated with individual stages. To view the KPIs for a specific stage, click the trend icon on the stage header.

KPIs in the Flow view are displayed at the time window you configure for each KPI. For example, you can configure an "Orders Placed" KPI to show data for the last 24 hours compared to the same period a week ago, or a "Revenue" KPI to show the last week compared to the prior week. For more information, see [Add a KPI](https://docs.newrelic.com/docs/pathpoint/kpis#add-a-kpi).

**Stages**

![A screenshot showing four stages, highlighted, each color-coded by health status.](https://docs.newrelic.com/images/pathpoint-stages.webp "Stages")

Stages represent the major phases of your business journey, such as Shop, Order, Notify, and Deliver. Each stage rolls up the health, congestion, throughput, and infrastructure state of all the services running beneath it, giving you a single, consolidated view of how that part of the business is performing.

In the Flow view, stages are color-coded to reflect their current health: green (healthy), yellow (warning), red (critical), or grey (unknown). This lets you immediately spot which phase of the journey is experiencing issues, without having to dig through individual services.

For more information on how health is calculated, see [Health indicators](https://docs.newrelic.com/docs/pathpoint/health-indicators).

**Levels and steps**

![A screenshot showing numbered levels within a stage, each summarizing the health of its steps.](https://docs.newrelic.com/images/pathpoint-levels-and-steps.webp "Levels and steps")

Steps break down each stage into the specific activities that make up that phase of the journey. Within a stage, steps are organized into numbered levels that reflect their sequential order, making it easy to understand dependencies and trace where an issue is occurring.

Each step displays a summary of its signal health. Click any step to expand it and see the individual signals contributing to its status, along with their source type, such as an alert, workload, or APM entity.

**Signals**

![A screenshot showing individual signals within a level, each with its name and source type.](https://docs.newrelic.com/images/pathpoint-signals.webp "Signals")

Signals are the most granular layer of a flow. Each signal maps to a specific entity or alert and reflects its current health. Signals roll up into steps, which roll up into stages, so a problem at the signal level surfaces all the way up the journey.

Signals are color-coded by health status. For more information, see [Health indicators](https://docs.newrelic.com/docs/pathpoint/health-indicators).

Click any signal to open its detail panel and view golden signals and open alert events, directly in context, without leaving the flow.

> #### 💡 NOTE
>
> The detail panel shows open alert events from the last 3 days.

Use the toggles in the top right of the Flow view to control which steps and signals are shown based on their health state: **Expand critical only**, **Expand unhealthy only**, or **Expand all**. Steps excluded from the level status rollup stay hidden regardless of which toggle is active.

## Signal error indicators [#signal-error-indicators]

![A screenshot showing a stage warning banner for signals that aren't reporting data.](https://docs.newrelic.com/images/pathpoint-signal-not-reporting.webp "Some entities aren't reporting")

The signals that make up a flow can change over time. When Pathpoint detects an issue with the signals in a stage, a warning indicator appears at the top of the affected stage.

There are two signal warnings you may encounter:

-   **Missing signals**: A signal that was included in the flow no longer exists in New Relic. Click the warning icon to see the list of missing signals for that stage. In the modal, click **Update signals** to open the signals overlay and make the necessary adjustments.
-   **No access**: Because different users may have access to different data scopes, a flow may contain data from accounts you don't have access to, so that data isn't visible to you. This indicator is purely informational, and appears at the top of the affected stage to let you know you're seeing only partial data there.

## Audit a change [#audit-a-change]

The audit log records who changed a flow and when. It doesn't record what changed.

To open it, select **Audit** from the **...** menu in the top right of the flow.

## View as code [#view-as-code]

You can view and manage your flows as code using NerdGraph or Terraform. To open the code preview, select **View as code** from the same menu.

It gives you five options:

-   **Terraform**: View the Terraform configuration for this flow. Use this to manage your flow as infrastructure-as-code and version-control your Pathpoint setup.
-   **Update with NerdGraph**: Preview the NerdGraph mutation that updates this flow's current configuration.
-   **Create with NerdGraph**: Preview the NerdGraph mutation that creates this flow from scratch. Use this as a starting point for automating flow creation.
-   **Query with NerdGraph**: Preview the NerdGraph query that retrieves this flow's configuration. Useful for auditing or building integrations on top of Pathpoint data.
-   **Export as JSON**: Export the flow as JSON.

For the full references, see [NerdGraph tutorial: Create and manage Pathpoint flows](https://docs.newrelic.com/docs/apis/nerdgraph/examples/nerdgraph-pathpoint-flows) and the [`newrelic_pathpoint_flow`](https://registry.terraform.io/providers/newrelic/newrelic/latest/docs/resources/pathpoint_flow) Terraform resource.

## Migrate a flow [#migrate-a-flow]

You migrate each flow from your existing version of Pathpoint to the updated version of Pathpoint by exporting its configuration and recreating it. The original flow stays where it is.

### Export and recreate a flow [#migrate-by-export]

1.  Open a flow and from the **...** menu, select **Export flow**.
2.  Choose a format:
    -   **JSON**: The raw flow document, useful for backup or inspection.
    -   **NerdGraph**: A ready-to-run mutation that recreates the flow.
    -   **Terraform**: Manage the flow as code with the New Relic Terraform provider.
3.  Copy the output, or click **Download**.

Then create the flow in the updated version of Pathpoint from that configuration. See [Import a flow](https://docs.newrelic.com/docs/pathpoint/create-manage-flows#create-from-json).

### What doesn't come across [#migration-limitations]

The updated version of Pathpoint supports KPIs on event data. These KPIs aren't migrated:

-   KPIs built on metric data
-   KPIs whose NRQL contains a subquery
-   KPIs belonging to an account other than the flow's own

> #### ⚠️ IMPORTANT
>
> A dynamic filter targeting alert conditions still migrates, but its health resolves to grey (unknown), since dynamic filters can't target alert conditions in the updated version of Pathpoint.