The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Thanks @Amelie Wisniak

Would be good to have this for GA release.

Is there any guidance you can give though, like in general, on average, ball park figure for each level of data how much storage would be used for low /  middle / high flow sizes (which is a measure of number of actions)?

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We are working on gathering some metrics. We'll let you know as soon as we have data to share. 

Thanks for your patience! 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-12-2024 18:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Thanks @Amelie Wisniak

Would be good to have this for GA release.

Is there any guidance you can give though, like in general, on average, ball park figure for each level of data how much storage would be used for low /  middle / high flow sizes (which is a measure of number of actions)?

------------------------------
Anton Vroon

Original Message:
Sent: 05-10-2024 11:28
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-10-2024 10:31
From: Vick Sweeney
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

------------------------------
Vick Sweeney
Hydro Quebec

Original Message:
Sent: 05-09-2024 21:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

------------------------------
Anton Vroon

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak - Thank you for helping gather metrics and other ways to track the data usage/storage associated with this much appreciated feature. When you do land on a way to track this information, it would be ideal to see the current usage/storage information visible directly on the main Flow Execution Data page.

A few questions in the interim:

1. For this beta period, do you have insight on the backend into how much data we are currently using (if we ask you for it directly)? That might help us proactively compile some estimates.
2. Will we incur data usage/storage fees during the beta? I ask because I want to set our logging level at Notes to see a bit more data than the Base level provides.
3. Once this is GA'd and the billing period is up, will we see the execution data usage/storage information show up in the Storage section of the Billing & Usage page?

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology

Original Message:
Sent: 05-14-2024 16:48
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

We are working on gathering some metrics. We'll let you know as soon as we have data to share. 

Thanks for your patience! 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-12-2024 18:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Thanks @Amelie Wisniak

Would be good to have this for GA release.

Is there any guidance you can give though, like in general, on average, ball park figure for each level of data how much storage would be used for low /  middle / high flow sizes (which is a measure of number of actions)?

------------------------------
Anton Vroon

Original Message:
Sent: 05-10-2024 11:28
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-10-2024 10:31
From: Vick Sweeney
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

------------------------------
Vick Sweeney
Hydro Quebec

Original Message:
Sent: 05-09-2024 21:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

------------------------------
Anton Vroon

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

@Amelie Wisniak - Bumping this question...thoughts or updates?

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology

Original Message:
Sent: 05-23-2024 09:36
From: Brian Jones
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Amelie Wisniak - Thank you for helping gather metrics and other ways to track the data usage/storage associated with this much appreciated feature. When you do land on a way to track this information, it would be ideal to see the current usage/storage information visible directly on the main Flow Execution Data page.

A few questions in the interim:

1. For this beta period, do you have insight on the backend into how much data we are currently using (if we ask you for it directly)? That might help us proactively compile some estimates.
2. Will we incur data usage/storage fees during the beta? I ask because I want to set our logging level at Notes to see a bit more data than the Base level provides.
3. Once this is GA'd and the billing period is up, will we see the execution data usage/storage information show up in the Storage section of the Billing & Usage page?

------------------------------
Brian T. Jones | Ascension | Senior Specialist - Technology

Original Message:
Sent: 05-14-2024 16:48
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

We are working on gathering some metrics. We'll let you know as soon as we have data to share. 

Thanks for your patience! 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-12-2024 18:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Thanks @Amelie Wisniak

Would be good to have this for GA release.

Is there any guidance you can give though, like in general, on average, ball park figure for each level of data how much storage would be used for low /  middle / high flow sizes (which is a measure of number of actions)?

------------------------------
Anton Vroon

Original Message:
Sent: 05-10-2024 11:28
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Anton Vroon @Vick Sweeney 

There are a lot of parameters that can impact your storage usage. It depends on the Execution Data flow level (Base, Notes, Verbose Notes, or All) and your flow specificities (e.g. flow size, number of actions, size of the variables, number of loops, etc.). We are exploring ways to help you track this usage better, but this is not part of the scope of this beta. In the meantime, we suggest you keep the level to the minimum you need and temporarily override individual flow levels when necessary.

When updating the level from "all" to "none", we do not delete previous instances but historical execution data is automatically deleted after 10 days. 

------------------------------
Amelie Wisniak
Genesys - Employees

Original Message:
Sent: 05-10-2024 10:31
From: Vick Sweeney
Subject: Beta - Advanced Architect Execution Data & Replay Mode

@Amelie Wisniak  in addition to Anton's question, will there be an indication anywhere of how much data is consumed by this feature, how much per flow, etc?  Will there be tools to manage that data?  If I put a flow in "All" mode for debugging purposes and then turn it back to None I'm assuming that all previous data will be deleted.  Is this the case?

All to say that we need to have tools to manage the data and better understand how we will be able to.  Just giving us a warning that it counts towards our fair use policy is not enough.

I hope this helps.  Thanks!

------------------------------
Vick Sweeney
Hydro Quebec

Original Message:
Sent: 05-09-2024 21:03
From: Anton Vroon
Subject: Beta - Advanced Architect Execution Data & Replay Mode

Hi Amelie,

Do we have any indication of what the storage impact/requirements will be. Ie on Average for a low / medium / high sized flow (as measured by architect), you should expect x Kbs per conversation? 

------------------------------
Anton Vroon

Original Message:
Sent: 05-09-2024 17:50
From: Amelie Wisniak
Subject: Beta - Advanced Architect Execution Data & Replay Mode

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Does this beta include a quicker way to get into the historical debugger other than (get ID manually, go into Architect, wait, manually search by ID, select it, wait more), like, a link in the Interaction view?

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

Hi,

Last week I filled in the enrollment form to participate the beta. But I see no Execution Data item in the menu in Architect. Is the beta not active in my Org? Or is there a permission tied to this feature?

Thanks,

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit under the Genesys Cloud fair use policy. Historical execution data storage is disabled by default. All users must enable this feature to use it and republish flows to track execution data.

Administrators and developers can access historical flow execution data via the Genesys Cloud Platform API, Architect Replay Mode, and the Genesys Cloud notifications service.

Learn more: Historical execution data overview - Genesys Cloud Resource Center

#BetaAnnouncement
#BetaUpdate
#NowRecruiting

------------------------------
Amelie Wisniak
Genesys - Employees
------------------------------

We joined the beta today. Finding it really useful, already helped solve a few bugs. It's not been seamless but definitely very good.

Immediate ask: can we get more information in the Execution History page when you click the Execution History button in a flow? Even just ConversationId (if not things like ANI, DNIS, ...) to help identify the interaction we want to review (without having to get the ID, search for it etc).

The Advanced Architect Execution Data & Replay Mode feature teams are pleased to announce our new beta has started! 

Genesys Cloud now offers advanced execution data capabilities for all Architect flow types. The enhanced capabilities give users greater control over how they use historical execution data and enable them to better understand user journeys and improve and troubleshoot their flows. Users can now decide whether to turn execution data storage on or off and choose from the following four different data levels:

• Base: understand high-level user journeys through actions and navigated menus, errors, and events.
• Notes: troubleshoot flows using variable values (includes the Base level).
• Verbose Notes: access conversation content with communications values (includes the Notes level).
• All: troubleshoot flows using action input and output values (includes the Verbose Notes level).

Historical execution data counts toward an organization's data storage limit u