Genesys Cloud - Main

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior? 

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

What's the size of the flow? 

If you hover over the "search flow" bar there's a little pop up that will tell you, then you can use the below as a reference.

https://help.mypurecloud.com/articles/architect-flow-size/

I'd imagine that your network upload speed could be a factor here as well. Do you have a way to test your speed out to the internet?

------------------------------
Dean Thames
Koch Business Solutions
------------------------------

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Version 90 something. Size is medium and it will not save or publish. We're well within the parameters. This issue is happening to everyone whos working out of the same call flows from different locations so I doubt its the network connection. Thoughts?

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 05-19-2021 12:19
From: Dean Thames
Subject: Architect won't publish/save call flow (medium size)

What's the size of the flow?

If you hover over the "search flow" bar there's a little pop up that will tell you, then you can use the below as a reference.

https://help.mypurecloud.com/articles/architect-flow-size/

I'd imagine that your network upload speed could be a factor here as well. Do you have a way to test your speed out to the internet?

------------------------------
Dean Thames
Koch Business Solutions

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services
------------------------------

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

That's interesting... If you could publish the flow but another person could not, that seems like a permission gap. Maybe there's a function in the flow that they don't have the full rights to make changes to?

------------------------------
Dean Thames
Koch Business Solutions
------------------------------

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

No sir. Our developers are who built the flow can no longer save or publish it. This is happening on more than one flow. It happens when we start adding reusable tasks. We also have multiple people saving to a flow sometimes. Since the system allows it we assumed it wouldn't cause issues. Maybe its that. Its definitely a genesys system issue that they've identified. I'm curious if there is anyone else out there having this issue and if there is a work around we don't know about?

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 05-20-2021 10:28
From: Dean Thames
Subject: Architect won't publish/save call flow (medium size)

That's interesting... If you could publish the flow but another person could not, that seems like a permission gap. Maybe there's a function in the flow that they don't have the full rights to make changes to?

------------------------------
Dean Thames
Koch Business Solutions

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

I asked the developper to capture a network trace with his browser (so called har file) during the issue and we observed a 500 error coming back from Genesys Cloud by using Google HAR Analyser.
If it was a permission issue I assume we would have a 40x error that we could have worked around.

But by checking again today the timestamps of the har file, I have a 17,364 seconds of 'sending time' on the request (it was a huge flow with complex ivr).
This 5s timeout could explain why it was failing, during the covid19 lockdown our developper was using his own dsl internet access whereas I'm using a fiber channel one.

------------------------------
Loïc Hesling
Orange Business Services
------------------------------

Original Message:
Sent: 05-20-2021 10:44
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

No sir. Our developers are who built the flow can no longer save or publish it. This is happening on more than one flow. It happens when we start adding reusable tasks. We also have multiple people saving to a flow sometimes. Since the system allows it we assumed it wouldn't cause issues. Maybe its that. Its definitely a genesys system issue that they've identified. I'm curious if there is anyone else out there having this issue and if there is a work around we don't know about?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 10:28
From: Dean Thames
Subject: Architect won't publish/save call flow (medium size)

That's interesting... If you could publish the flow but another person could not, that seems like a permission gap. Maybe there's a function in the flow that they don't have the full rights to make changes to?

------------------------------
Dean Thames
Koch Business Solutions

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

This is excellent information. We're being told the exact same thing after seeing our HAR file. We have a team of developers all experiencing the same thing so its definitely a system limitation. Our call flow is only half way done and we're dead in the water until this is resolved. We've consolidated as much as we can. The call flow size (medium) is well within their parameters so idk. We can't afford a month of nothing though that's for sure.

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 05-20-2021 11:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I asked the developper to capture a network trace with his browser (so called har file) during the issue and we observed a 500 error coming back from Genesys Cloud by using Google HAR Analyser.
If it was a permission issue I assume we would have a 40x error that we could have worked around.

But by checking again today the timestamps of the har file, I have a 17,364 seconds of 'sending time' on the request (it was a huge flow with complex ivr).
This 5s timeout could explain why it was failing, during the covid19 lockdown our developper was using his own dsl internet access whereas I'm using a fiber channel one.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:44
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

No sir. Our developers are who built the flow can no longer save or publish it. This is happening on more than one flow. It happens when we start adding reusable tasks. We also have multiple people saving to a flow sometimes. Since the system allows it we assumed it wouldn't cause issues. Maybe its that. Its definitely a genesys system issue that they've identified. I'm curious if there is anyone else out there having this issue and if there is a work around we don't know about?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 10:28
From: Dean Thames
Subject: Architect won't publish/save call flow (medium size)

That's interesting... If you could publish the flow but another person could not, that seems like a permission gap. Maybe there's a function in the flow that they don't have the full rights to make changes to?

------------------------------
Dean Thames
Koch Business Solutions

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services
------------------------------

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

HI Loic, 

Do you have any metrics or additional information around that... i.e., what their upload speed was or what type of internet connection they had? 

Thanks
Dean.

------------------------------
Dean Thames
Koch Business Solutions
------------------------------

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell. 

Thanks,

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Bryan,

We currently have a new feature in Beta called Common Modules for Architect.  Common Modules are kind of like reusable tasks but they are an independent flow.  This would allow you to break up your monolithic Architect flow into several smaller flows.  For instance each sub-menu on your main flow could invoke it's own Common Module and one Common Module can call another.  This would definitely help with the saving problem because your call flows would no longer be huge.

You should talk to your reseller to see if they can get the Common Module beta enabled on your org.  It will likely go GA in 2-3 weeks.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com
------------------------------

Original Message:
Sent: 06-03-2021 17:45
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell.

Thanks,

------------------------------
Bryan De La Cruz

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

I apologize because my previous post about Common Modules was wrong.  Those Common Modules are actually copied into the Call Flow that uses them.  It is a nice feature that helps break up monolithic flows into component parts, but apparently it works differently under the covers than I was aware of.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com
------------------------------

Original Message:
Sent: 06-04-2021 13:17
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

Bryan,

We currently have a new feature in Beta called Common Modules for Architect.  Common Modules are kind of like reusable tasks but they are an independent flow.  This would allow you to break up your monolithic Architect flow into several smaller flows.  For instance each sub-menu on your main flow could invoke it's own Common Module and one Common Module can call another.  This would definitely help with the saving problem because your call flows would no longer be huge.

You should talk to your reseller to see if they can get the Common Module beta enabled on your org.  It will likely go GA in 2-3 weeks.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-03-2021 17:45
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell.

Thanks,

------------------------------
Bryan De La Cruz

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Was in this discussion literally 30 minutes ago.

So there is copy and paste coming, but the modules are not separate reusable ala Designer in Engage Cloud?

Hi Kevin,

We're talking about Genesys Cloud.

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 06-04-2021 14:15
From: Kevin Brown
Subject: Architect won't publish/save call flow (medium size)

Was in this discussion literally 30 minutes ago.

So there is copy and paste coming, but the modules are not separate reusable ala Designer in Engage Cloud?

------------------------------
Kevin Brown
Cognizant Technology Solutions

I've been working and playing with Genesys since 1995
Arizona, USA

Original Message:
Sent: 06-04-2021 13:41
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

I apologize because my previous post about Common Modules was wrong.  Those Common Modules are actually copied into the Call Flow that uses them.  It is a nice feature that helps break up monolithic flows into component parts, but apparently it works differently under the covers than I was aware of.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-04-2021 13:17
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

Bryan,

We currently have a new feature in Beta called Common Modules for Architect.  Common Modules are kind of like reusable tasks but they are an independent flow.  This would allow you to break up your monolithic Architect flow into several smaller flows.  For instance each sub-menu on your main flow could invoke it's own Common Module and one Common Module can call another.  This would definitely help with the saving problem because your call flows would no longer be huge.

You should talk to your reseller to see if they can get the Common Module beta enabled on your org.  It will likely go GA in 2-3 weeks.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-03-2021 17:45
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell.

Thanks,

------------------------------
Bryan De La Cruz

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Bryan,

Understood. My clarification to Jim is that this is just a copy/paste into a single flow and not a separate module (much like a call flow in Cloud) as it is in Engage Cloud?  If so, then that doesn't fix this problem.

Architect already has copy/paste.
https://help.mypurecloud.com/articles/work-with-architect-editing-tools/

------------------------------
Melissa Bailey
Genesys - Employees
------------------------------

Original Message:
Sent: 06-04-2021 14:15
From: Kevin Brown
Subject: Architect won't publish/save call flow (medium size)

Was in this discussion literally 30 minutes ago.

So there is copy and paste coming, but the modules are not separate reusable ala Designer in Engage Cloud?

------------------------------
Kevin Brown
Cognizant Technology Solutions

I've been working and playing with Genesys since 1995
Arizona, USA

Original Message:
Sent: 06-04-2021 13:41
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

I apologize because my previous post about Common Modules was wrong.  Those Common Modules are actually copied into the Call Flow that uses them.  It is a nice feature that helps break up monolithic flows into component parts, but apparently it works differently under the covers than I was aware of.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-04-2021 13:17
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

Bryan,

We currently have a new feature in Beta called Common Modules for Architect.  Common Modules are kind of like reusable tasks but they are an independent flow.  This would allow you to break up your monolithic Architect flow into several smaller flows.  For instance each sub-menu on your main flow could invoke it's own Common Module and one Common Module can call another.  This would definitely help with the saving problem because your call flows would no longer be huge.

You should talk to your reseller to see if they can get the Common Module beta enabled on your org.  It will likely go GA in 2-3 weeks.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-03-2021 17:45
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell.

Thanks,

------------------------------
Bryan De La Cruz

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------

Agreed.

------------------------------
Bryan De La Cruz
------------------------------

Original Message:
Sent: 06-04-2021 14:15
From: Kevin Brown
Subject: Architect won't publish/save call flow (medium size)

Was in this discussion literally 30 minutes ago.

So there is copy and paste coming, but the modules are not separate reusable ala Designer in Engage Cloud?

------------------------------
Kevin Brown
Cognizant Technology Solutions

I've been working and playing with Genesys since 1995
Arizona, USA

Original Message:
Sent: 06-04-2021 13:41
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

I apologize because my previous post about Common Modules was wrong.  Those Common Modules are actually copied into the Call Flow that uses them.  It is a nice feature that helps break up monolithic flows into component parts, but apparently it works differently under the covers than I was aware of.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-04-2021 13:17
From: Jim Crespino
Subject: Architect won't publish/save call flow (medium size)

Bryan,

We currently have a new feature in Beta called Common Modules for Architect.  Common Modules are kind of like reusable tasks but they are an independent flow.  This would allow you to break up your monolithic Architect flow into several smaller flows.  For instance each sub-menu on your main flow could invoke it's own Common Module and one Common Module can call another.  This would definitely help with the saving problem because your call flows would no longer be huge.

You should talk to your reseller to see if they can get the Common Module beta enabled on your org.  It will likely go GA in 2-3 weeks.

------------------------------
Jim Crespino
Senior Director, Developer Evangelism
Genesys
https://developer.genesys.com

Original Message:
Sent: 06-03-2021 17:45
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

I'll keep you posted on what they come back with on ours. I'm sure they can see all this so it's hard to imagine they get back to us with something different. Currently our reseller has escalated it and the work around provided has been serving its purpose. We are a very large customer and multiple engineers have had the same problem so to bandwidth is a tough sell.

Thanks,

------------------------------
Bryan De La Cruz

Original Message:
Sent: 06-03-2021 03:36
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

I'm not sure it is seen as an issue for Genesys.
We got a final explanation from our case opened to the support care team, to sum it up : work as design.

If there is anything at fault it is the internet connection our developper was using that is not powerful enough for the service to work.

------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-20-2021 10:49
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

Thank you for your reply. Its definitely an issue Genesys knows about. I think Genesys is seeing how many customers are impacted by this before they start talking about a future enhancement that addresses the issue. The issue happens after building the IVR to a certain size or version so I can't imagine how permissions would come into play. If it was permissions they wouldn't be able to build it the point it becomes corrupt right?

------------------------------
Bryan De La Cruz

Original Message:
Sent: 05-20-2021 09:31
From: Loic Hesling
Subject: Architect won't publish/save call flow (medium size)

Hello,

One of our script developper had a similar issue some time ago, we tried everything we could think of (cache clearing, browser change, other pc, and so on) but nothing worked.
To this day the case is still being investigated by the dev team, at least so I've been told in the support case (it's been a month).
We were lucky it was at the end of the development and not at the beginning but to be honest I'm kind of relieved that were not alone in this.

What did work though was changing of account : on the same flow I could make the changes that our script developper couldn't.

Regards



------------------------------
Loïc Hesling
Orange Business Services

Original Message:
Sent: 05-19-2021 12:00
From: Bryan De La Cruz
Subject: Architect won't publish/save call flow (medium size)

We're a large business building complex call flows and are dead in the water due to Architect performance issues. I'm curious to see if anyone else has experienced this behavior?

Problem Description:

Recently when attempting the save (and then Publish) the Dep_Enterprise_Inbound_Call_Flow Flow in Architect, it "time" for a short
while and the Flashes failed save (or failed Publish). When it first started happening it would happen, I would retry a few time and event
ually it would successfully save and/or Publish. But, today I have been unable to Save or Publish this Flow. I have been trying for over a
n hour. I did log out (had to click on "disgard changes" to leave the flow), closed Chrome, and logged back in. But, I am still
unable to save / Publish this flow. All developers were in a meeting today and I had everyone log out of architect. I was the only person
in architect and was still unable to save / publish this flow. The "Failed save" and/or "Failed Publish" just flashes f
or a seconds or 2 and goes away. There is not other indication the save and /or publish failed.

Genesys response after looking at logs

The issue is that the request body is taking longer than the 5 seconds allotted to be uploaded to the cloud. The 5 seconds is not a new timeout and upping the limit could have adverse effects to the platform.

#Ask Me Anything (AMA)
#ArchitectureandDesign
#Connect with a Customer (NEW)
#Implementation
#PlatformAdministration
#SystemAdministration

------------------------------
Bryan De La Cruz
------------------------------