Feature coming soon

Genesys Cloud offers access to comprehensive historical execution data for all Architect flow types. For more information, see Historical execution data overview.

Genesys Cloud disables historical execution data storage by default. To enable storage, follow these steps:

  1. Click Admin.
  2. Under Account Settings, click Organization Settings.
  3. On the Settings tab, scroll down to the Execution Data section.
  4. Under Execution Data, use the toggle to enable execution data storage for your organization. A disclaimer message appears that informs you that Genesys Cloud may store sensitive information.
  5. Click Yes to enable storage.

To navigate to Admin > Account Settings > Organization Settings > Settings from Architect, click Help and select Execution Data Settings.

Note: Configure the data types for which you want to store execution data. If Architect Flows is disabled, Genesys Cloud does not store execution data for Architect flows.

To configure the data types for which to store historical execution data, follow these steps:

  1. Click Admin.
  2. Under Account Settings, click Organization Settings.
  3. On the Settings tab, scroll down to the Execution Data section.
  4. Under Execution Data Storage, use the Architect Flows toggle to enable execution data storage for the data type.

To navigate to Admin > Account Settings > Organization Settings > Settings from Architect, click Help and select Execution Data Settings.

To set the execution data level for your organization, follow these steps:

  1. Click Admin.
  2. Click Architect.
  3. Under Help, select Execution Data Flows Level. The Set Execution Data Level for Flows window appears.

You can choose not to track execution data or select from four different levels of execution data granularity:

    • Base: understand high-level user journeys through Architect actions and navigated menus, errors, and events.
    • Notes: optimize Architect flows using variable values (includes the Base level).
    • Verbose Notes: access conversation content with communication values (includes the Notes level).
    • All: troubleshoot through action input and output values (includes the Verbose Notes level).
  1. Select your preferred execution data level.
  2. Click Save.

To override the organization-level data setting for a specific flow, follow these steps:

  1. Click Admin.
  2. Click Architect.
  3. Click or hover over the Flows menu and select your flow’s flow type.
  4. Select the checkbox next to the flow that you want to override the organization-wide execution data level for.
  5. Click Execution Data. The Override Execution Data Flow Level window appears.

You can choose not to track execution data or select from four different levels of execution data granularity:

    • Base: understand high-level user journeys through Architect actions and navigated menus, errors, and events.
    • Notes: optimize Architect flows using variable values (includes the Base level).
    • Verbose Notes: access conversation content with communication values (includes the Notes level).
    • All: troubleshoot through action input and output values (includes the Verbose Notes level).
  1. Select your preferred data setting. You can see your organization’s data setting under the Execution Data Flow Level option.
  2. Click Save.