Genesys Cloud - Main

Hello

I would use the new feature Execution history. Historical execution data overview - Genesys Cloud Resource Center (mypurecloud.com). Assign a number to the flow, activate execution data and then call inn. Look in the history on how the flow went. I have used this a lot during development of new flow and it is a very good tools to debug a flow

I concur with the Execution Data method. It gives you a lot more detail on what happened when the flow ran, and should also show you what errors you encounter.

Hello

I would use the new feature Execution history. Historical execution data overview - Genesys Cloud Resource Center (mypurecloud.com). Assign a number to the flow, activate execution data and then call inn. Look in the history on how the flow went. I have used this a lot during development of new flow and it is a very good tools to debug a flow

Hello

I would use the new feature Execution history. Historical execution data overview - Genesys Cloud Resource Center (mypurecloud.com). Assign a number to the flow, activate execution data and then call inn. Look in the history on how the flow went. I have used this a lot during development of new flow and it is a very good tools to debug a flow

Thank you Eystein for your reply.

I may be wrong, my understanding is - Execution history feature will allow me to use historical data for execution.

If I understood correctly, we are new to Genesys and don't have any historical execution data available with us. Also, I am not having DID number registered yet. That's why I am looking for alternatives to debug the flow, and found the debug option itself which is not working for me.

Hello

I would use the new feature Execution history. Historical execution data overview - Genesys Cloud Resource Center (mypurecloud.com). Assign a number to the flow, activate execution data and then call inn. Look in the history on how the flow went. I have used this a lot during development of new flow and it is a very good tools to debug a flow

You might have to add the permissions for that which are listed into the link above.  You should enable Genesys Cloud Voice and order a number for testing.  It only cost $2 and $1 a month.  You can't really rest your flows and system without calling into it from an external number 

Thank you Eystein for your reply.

I may be wrong, my understanding is - Execution history feature will allow me to use historical data for execution.

If I understood correctly, we are new to Genesys and don't have any historical execution data available with us. Also, I am not having DID number registered yet. That's why I am looking for alternatives to debug the flow, and found the debug option itself which is not working for me.

Hello

I would use the new feature Execution history. Historical execution data overview - Genesys Cloud Resource Center (mypurecloud.com). Assign a number to the flow, activate execution data and then call inn. Look in the history on how the flow went. I have used this a lot during development of new flow and it is a very good tools to debug a flow

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Hello

In organization setting at the bottom you find this

Eystein Kylland | Fagleder Tech | PM Digital Cloud Contact Centre Tech MGMT

DNB Bank ASA

Besøksadresse: Dronning Eufemias gate 30| 0191 Oslo

Mob: +47 934 81 805 | Kundeservice: 04800

Epost: eystein.kylland@dnb.no | www.dnb.no

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

@Vincent Sabolboro have you opened and republished the flows you're not seeing data for then made calls into them?  Was it you that enabled execution history data for this org or someone else?  The other possibility may be someone set the default level as None then explicitly set a level on your queues that do work with it to be something else.

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

@Vaun McCarthy

no I have not opened and republished any of the flow except for the one in-queue flow and one bot flow. All the in-queue flows and bot flow execution history are showing results even those that we did not do any update after setting the execution level. 

I tried both ways, enable execution level on the org level to "all" and just specific inbound flow to "all" with the same resul "No data available"

I will try to open and republish the inbound flow I need to troubleshoot as a workaround while waiting resolution from support. 

@Vincent Sabolboro have you opened and republished the flows you're not seeing data for then made calls into them?  Was it you that enabled execution history data for this org or someone else?  The other possibility may be someone set the default level as None then explicitly set a level on your queues that do work with it to be something else.

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>

Debugging also didn't work for me, until I followed this instruction (on https://help.mypurecloud.com/articles/test-a-flow/):

To create a debug version of a flow open the Publish menu and select Debug. The Debug Enabled dialog box opens with confirmation that the flow can be debugged.

Did you maybe miss that step?

Nick.

As a rule, any new features in Architect usually require you to open and republish the flows before that new feature may show up.

@Vaun McCarthy

opening then republishing the inbound flow fix the execution flow history for inbox flow. This will work for now for what I need.

Thank you. 

@Vaun McCarthy

no I have not opened and republished any of the flow except for the one in-queue flow and one bot flow. All the in-queue flows and bot flow execution history are showing results even those that we did not do any update after setting the execution level. 

I tried both ways, enable execution level on the org level to "all" and just specific inbound flow to "all" with the same resul "No data available"

I will try to open and republish the inbound flow I need to troubleshoot as a workaround while waiting resolution from support. 

@Vincent Sabolboro have you opened and republished the flows you're not seeing data for then made calls into them?  Was it you that enabled execution history data for this org or someone else?  The other possibility may be someone set the default level as None then explicitly set a level on your queues that do work with it to be something else.

@Eystein Kylland

Can you clarify what you mean by "Activated in systemconfig", maybe upload screen capture if possible. 

@Nick Tait

Is execution history also not working for you for inbound flow and works for in-queue flow? if yes then we have the same issue, inbound execution history is just showing "No data available" and works for in-queue flows and bot flows. 

I have been working for Genesys Support for more than a week now still no resolution. 

<gux-table-beta compact="compact" id="query-results-table" emptymessage="Query did not find any flow instances" data-inintest="execution-query-results-table" gs-table-id="gux-table-ttlzyxg17p" gs-compact="" hydrated=""></gux-table-beta>