Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 82937]
Primary programming language affected, if applicable [ID: 82936]
[ID: 82935]
[ID: 82940]
[ID: 82941]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
To be able to configure the session expiration time for the Dialogflow CX agent globally, through the Dialogflow CX console interface, without having to modify each individual intent. Currently, the default session timeout is set to 30 minutes, and need to extend it to 2 hours for the use case. This should be a project-level or agent-level setting that applies to all interactions with the agent.
This clearly states the desired outcome – a way to change the session timeout globally via the console.
-- Detailed functionality description (How might it work? What needs to be changed?) --
I envision a new setting within the Dialogflow CX console that would allow users to specify a global session expiration time. This could be located under the agent's settings or within the project configuration. The setting should allow for users to select a session duration from a set of predetermined options or to specify a custom duration. For example, there could be options like: 30 minutes (default), 1 hour, 2 hours, or a custom input.
Once the session time out is set, this change should apply across all integrations of the Dialogflow CX agent, and no API changes on a per-intent basis should be needed. This functionality should be implemented at the project or agent level so all sessions of the agent will be able to use the updated session expiration. This will not be applied in any specific integration setting only.
This provides specific suggestions for how the feature might work, including a place to find the setting and how it should be implemented. It emphasizes the global application, the available setting should have some options to choose from or a custom value as well. This will provide flexibility for other users also.
-- If applicable, reasons why alternative solutions are not sufficient --
Currently, the only method available for increasing the session timeout is via the API by passing a session_ttl for each intent but this leads to maintenance overhead as it requires multiple API calls for every intent to extend the session. The goal is to get away from handling this on the intent level to a more global/project level setting for simplicity of implementation.
-- Other information (workarounds you have tried, documentation consulted, etc) –
Reviewed the Dialogflow CX documentation regarding session management
Currently using the workaround by passing session_ttl using the API for each intent. However, this is not scalable.