How to
Navigate the Experience details page

Alex Pribula
Alex Pribula
  • Updated

The Experiences details page provides a detailed timeline of all activitiesTooltip within an experience. This article offers steps on navigating this page, understanding and troubleshooting the experience.

Accessing Experience details

  1. From the Flow details page, select the Experiences tab, and click on the view icon next to any experience listed.
  2. In the Experience explorer, you can identify the current state of the experience and other comprehensive information including experience start and end times, a detailed timeline of activity.

The Experience details pane provides a highlight of the experience. 

Experience explorer

experience explorer.png

The experience explorer provides a detailed timeline of all activity for an experience.

How to use the experience explorer

  1. In the first column, click on a node to view the activity data within. This column displays all the nodes an experience has progressed through. The most recent node is displayed at the top.
  2. For Node activity viewing, click on an activity to view details, as indicated by a forward arrow icon. This column displays all activities within the node, the most recent at the top.

Understanding each activity

Experience activity

An experience is always marked by a start and end activity, in addition to any activity from nodes in between. 

unbranded-experience activity

    • Experience started: The experience has started. It contains the data as entered in the trigger node used to initiate it."
    • Experience retried: The experience has encountered an issue, and is expected to affected other experiences too. A common example is a field missing from a Criteria Split node. The experience will make limited retry attempts before marking itself as an error.
    • Experience errored: The experience has ended mid-flow after failing retry attempts from an irrecoverable issue that will affect other experiences as well. For example, this can occur from an incorrect credential in the Make a web request node.
    • Experience completed: The experience has successfully reached the end of the flow, meeting an outcome path from each node it progresses through.
    • Experience failed: The experience has ended mid-flow, unable to meet any of the outcome paths from the node where it was stopped.

Node activity

An actionTooltip nodes is always marked by a start and end Activity. For some nodes, additional Activity can be tracked as described in the sections below.

custom node activities

    • Action started: The action node has started. It contains the data as entered in the node settings and other configuration settings.
    • Action ended: The action node has ended with a 'success' or 'failure' result.

Messaging

  • unbranded-Conversation node activities
    • Action started: The Conversation node has started. It contains information about the node and its configurations.
    • Message queued: The outbound SMS has been queued for sending to the gateway. Extensive information and a preview is available on this activity.
    • Message passed to gateway: The outbound SMS has been handed to the gateway for delivery.
    • Message rejected: The outbound SMS was rejected by the gateway and was not sent. Common examples include: carrier or network issues or blocked recipient. For a detailed troubleshooting guide, see Conversation node.
    • Message failed: The outbound SMS was not sent; the gateway made an attempt but delivery failed.
    • Reply matched: An inbound message matching a path in the Conversation node has been received. Extensive information and a preview is available on this activity.
    • Reply window elapsed: No matching inbound message was received within the configured time period.
    • Message validation failed: The outbound SMS could not be sent due to an invalid format. Common examples include incorrectly formatted or missing phone number. For a detailed
    • Action ended: The Conversation node has ended with a 'success' or 'failure' result.
  • unbranded-outbound SMS activities

    • Action started: The Outbound SMS node has started. It contains information about the node and its configurations.
    • Message queued: The message has been queued for sending to the gateway. Extensive information and a preview is available on this activity.
    • Message passed to gateway: The message has been handed to the gateway for delivery.
    • Message sent: The message has been sent to the recipient.
    • Message delivered: The message has been delivered to the recipient.
    • Message rejected: The SMS was rejected by the gateway and was not sent. Common examples include: carrier or network issues or blocked recipient. For a detailed troubleshooting guide, see Outbound SMS.
    • Message failed: The SMS could not be sent; the gateway made an attempt but delivery failed. For a detailed troubleshooting guide, see Outbound SMS.
    • Message validation failed: The SMS could not be sent due to an invalid format. Common examples include incorrectly formatted or missing phone number. For a detailed troubleshooting guide, see Outbound SMS.
    • Action ended: The Outbound SMS node has  has ended with a 'success' or 'failure' result.
  • unbranded-outbound email activities
    • Action started: The email node has started. It contains information about the node and its configurations.
    • Message queued: The email has been queued for sending to the gateway. Extensive information including attachment names, and a preview is available on this activity.
    • Message passed to gateway: The message has been handed to the gateway for delivery.
    • Message delivered: The email has been confirmed as delivered to the recipient.
    • Message opened: An email has been opened.
    • Message clicked: An email link has been clicked on for the first time. Subsequent clicks will not be recorded.
    • Message rejected: The email was rejected by the gateway. Examples include: invalid email address, spam filtering, full mailbox, unsubscribed/blocked, attachment size exceed and bounced. For a detailed trouble shooting guide, see Outbound email.
    • Message failed: The email failed to be delivered; the gateway made an attempt but delivery failed.
    • Message sent: The email has been sent from the gateway to the recipient.
    • Message validation failed: The email was rejected due to an invalid format. Common examples include incorrectly formatted or missing email. For a detailed troubleshooting guide, see Outbound email.
    • Action ended: The email node has ended with a 'success' or 'failure' result.

Data

  • unbranded-make a web request activities

    • Action started: The Make a web request node has started. It contains the request details, headers and body.
    • Action ended: The intelligence node has ended. It contains the payload detailing the response, code, outcome and outcome reason. For more details, see Make a web request.

Intelligence

All intelligence suite nodes (Generate Experiment, Generate Content, Identify Next Best Offer, Natural Language Processing, Global Request, and Segment Customer nodes) are marked by a start and end activity.

  • unbranded-intelligence node activities

    • Action started: The intelligence node has started. It contains the design prompt and other node configuration settings.
    • Action ended: The intelligence node has ended. It contains the payload including the content generated by the node.

Workflow

  • unbranded-criteria node activities
    • Criteria evaluated: The experience has fulfilled a criteria path.