How to
Navigate the Flow details page

Alex Pribula
Alex Pribula
  • Updated

Navigate Flows page in Workflow Studio

The Flow details page shows in-depth information about each flow. This article offers steps on navigating this page, understanding the flow’s state and its experiences, and utilising available editing options.

Viewing flow information

  1. To begin, click on the eye icon next to any flow listed on the Flows page. This will open the Flow details, where you'll find comprehensive information, including the flow's title, current state, and a brief description if provided. You'll also be able to view flow activity if the flow has been activated.
  2. You can identify the current state of your flow, whether the flow is in use (Active), being designed (Draft), ended (Terminated), or facing issues (Error).

Flow overview tab

The Flow overview tab shows your flow configuration and its high-level summary.

Activity summary

activity statistics.png

The Activity summary provides a count of total, active, completed and failed Experiences for the selected flow version. This summary is available for activated flows. Hover over the count to view the full count, and refresh to view latest updates.

The following details are available for each flow:

  • Total experiences: The number of experiences started from the first node.
  • Complete experiences: The number of experiences that successfully reached the end of the flow, passing through each of the node's outcome paths.
  • Failed experiences: An experience ends mid-flow if it cannot meet any of the outcome paths from the current node. For example, an email bounces and no fallback path is configured. You can enable outcome paths on nodes to continue experiences in these cases.
  • Experience errored: An experience ends due to an unrecoverable issue that affects other experiences, which can be caused by external dependencies (e.g., invalid API credentials).

Flow preview and Experience breakdowns

progress trackers.png

 

The Flow preview shows the flow design, configuration and a breakdown of experience progress.

You can use the Experience breakdown statistics beneath each node to determine the points that experiences have reached, and what paths they have taken. At the end of each path, there is a number of experiences that successfully reached the end (Complete).

Selecting a node will show it's read-only configuration.

Experiences tab

The Experiences tab provides an overview of the experiences in the flow and a high-level summary of your experiences.

The Experiences table lists each individual experience started for the flow version, sorted by the most recent first. You can page

The following details are available in the table:

  • Experience ID: A unique identifier of an experience.
  • Last processed action: The most recent actionTooltip taken by the experience.
  • Started: The date and time the experience started.
  • Status: The current status of the experience. For a detailed guide on Experience statuses, see Understanding Experience Lifecycle.
  • Action icons

Search functionality

search experiences.png

Use the search bar to quickly find Experiences by its details, time range and status. All results are will display all experiences that contain the search query.

Search results always display active experiences, while completed experiences appear only if they are within your data retention period.

The following options are available for refining your search based on specific criteria:

  • Experience ID: Find a specific experience by entering the exact Experience ID.
  • Experience status: Find experiences with one or more statuses, including active, completed, errored, and/or failed. A date range must be set.
  • Node: Find experiences that includes a specified node and its activities. A date range will search for the specified node activities that may occur outside of the experience end time. A date range must be set, and optionally one or more experience statuses. For a detailed guide on Node Activity, see Navigating the Experience details page.
  • Recipient phone: Find experiences with messages sent to or received from a phone number. The phone number should match exactly to the one provided through the trigger payload, or the recipient field of the node. A date range must be set, and optionally one or more experience statuses.
  • Recipient email: Find experiences with messages sent to an email address. The email address should match exactly to the one provided in the trigger payload or recipient field of the node. A date range must be set, and optionally one or more experience statuses.
  • Web request URL: Find experiences with a web request to a specific URL. The URL should match exactly to the one entered in the Make a Web Request node. A date range must be set, and optionally one or more experience statuses.

Flow versions pane

Flow versions pane provides a list all the versions of the flow, allowing you to review the past content and changes made to the flow by selecting different versions from the history.

For a detailed guide on flow states, see Understanding Flow versions and their management

 

Using edit and more options

To edit a flow, click the Edit button. This action is available for flows in Active and Draft state.

You can only edit flows that are currently active or in a draft state. If you click Edit a flow that has a draft on top (indicated by the 'Drafting' badge on the flow list) you will open the new draft flow version. For a detailed guide on this, see Editing activated flows

The More dropdown menu offers additional actions such as Archive, Unarchive, Delete, Duplicate, Drain, and Terminate, depending on the flow's status.

For a detailed guide on flow states, see Manage individual flows in various states

 

FAQ

Why does the experience show a "Message Failed" or "Message Rejected" event after progressing on the Sent path?

These events can occur later due to carrier delays. For instance, your messaging node (e.g. Conversation node) continues on the Sent path if no failures occur within the set wait time (e.g. 10 minutes). However, a 'Rejected' status might still be reported afterward if issues are detected later. You can configure the wait time in node outcomes.