Solved: Dialogflow CX environment specific webhook timeout... - Page 2

tojagrut · 03-07-2023 01:12 AM

Hello,

I am running into an issue with timeout value for environment specific webhooks in Dialogflow CX.

We have extended the timeout value to 15 seconds for the webhook and we have multiple environment specific webhook URLs set as well. You can see precise setup as part of this issue posted by another user facing the exact same issue 3 months back : https://issuetracker.google.com/issues/261683010

It seems like the webhook timeout value is not being considered for environment specific URLs. I see it does work for the agent level URL which is not what I would like to use as we have for obvious reasons different URL for non-prod and production apps.

Is there any workaround or possible solution to this problem?

Cheers, jags

tojagrut

Found a suitable workaround:

Update the default webhook URL to production with timeout 15 seconds. Remove the environment specific webhook URL.
Release a version of the flow and use it with the production environment.
Update the default webhook URL back to test endpoint with timeout 15 seconds.
Repeat the steps before releasing the new version for production usage.

When you release the version of a flow, Dialogflow CX would create the snapshot of webhook configuration as well along with flow. And when you update the default webhook URL again, it would only update for unpublished/draft version and it does not affect the webhook URL in the released version of the flow. It's verified and working approach!

Cheers, jags

View solution in original post

Dialogflow CX environment specific webhook timeout is not considered