Genesys Cloud - Main

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

https://help.genesys.cloud/articles/historical-execution-data-overview/
From the 2nd set of notes

• Genesys Cloud supports returning a maximum of 200 execution data instances per query. It is important to note that Genesys Cloud cannot guarantee that the query returns the most recent 200 execution instances.

Look them up by conversation id instead of flow when you get to 200

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

https://help.genesys.cloud/articles/historical-execution-data-overview/
From the 2nd set of notes

• Genesys Cloud supports returning a maximum of 200 execution data instances per query. It is important to note that Genesys Cloud cannot guarantee that the query returns the most recent 200 execution instances.

Look them up by conversation id instead of flow when you get to 200

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

https://help.genesys.cloud/articles/historical-execution-data-overview/
From the 2nd set of notes

• Genesys Cloud supports returning a maximum of 200 execution data instances per query. It is important to note that Genesys Cloud cannot guarantee that the query returns the most recent 200 execution instances.

Look them up by conversation id instead of flow when you get to 200

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

Hi Dianne,

I encounter the same problem now and then. I had a case open at Genesys support but without a result. It definitly has nothing to to with the 200 executions limit that  Meilissa mentioned. I have the same problem with brand new flows without 200 executions in history. As you observed the problem seems to occur with version changes. Sometimes on next day the inivsible executions are visible.

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!

Hi Dianne,

I encounter the same problem now and then. I had a case open at Genesys support but without a result. It definitly has nothing to to with the 200 executions limit that  Meilissa mentioned. I have the same problem with brand new flows without 200 executions in history. As you observed the problem seems to occur with version changes. Sometimes on next day the inivsible executions are visible.

Hi,

We use flow executions a lot and we've been noticing that some for some flows, execution history doesn't show the most recent version of that flow.

For example, I published version 57 of Flow A, then I place some test calls. When I click on Execution History, I can see instances from version 56 and below, but nothing for version 57. I've checked the execution data and setting, both look good. When I search for it using conversation id, it does show up.

Has anyone encountered this? Are we missing a config somewhere?

Thank you!