Yes that's correct. The setting won't change the timeout on the Dialogflow side, that is still currently limited to a max of 30 minutes. We do have an idea to resume these longer interactions past 30 minutes here: https://genesyscloud.ideas.aha.io/ideas/SSA-I-455
------------------------------
Justin Campbell
Product Manager
Genesys - Employees
------------------------------
Original Message:
Sent: 07-16-2023 04:36
From: Robert Wakefield-Carl
Subject: Follow-Up Response Timeout overrides DialogFlow CX session timeout
Although that says 0 to 10 hours, I don't think that this will change the timeout on the DialogFlow side. @Justin Campbell - what do you think. Is this only the control for the took in Architect or actually controlling DialogFlow timeouts?
------------------------------
Robert Wakefield-Carl
ttec Digital
Sr. Director - Innovation Architects
Robert.WC@ttecdigital.com
https://www.ttecDigital.com
https://RobertWC.Blogspot.com
Original Message:
Sent: 07-13-2023 13:07
From: Marco Ruzzon
Subject: Follow-Up Response Timeout overrides DialogFlow CX session timeout
Hi Community,
in the context of an integration between Architect and Google DialogFlow CX, is it confirmed that the "Follow-Up Response Timeout", which can be configured in the "Call Dialogflow CX Bot" action block, if set to a value greater than 30 minutes, can automatically keep alive the DialogFlow session that normally ends after 30 minutes?(according to Google documentation: https://cloud.google.com/dialogflow/cx/docs/concept/session#long-lasting)
Thank you
#ConversationalAI(Bots,AgentAssist,etc.)
#Integrations
------------------------------
Marco Ruzzon
Indra Italia spa
------------------------------