Dialogflow CX environment specific webhook timeout is not considered

[tojagrut]

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

[xavidop]

If this is the case,

My suggestions is going to be to export your current agent, import this agent into a newer one, change the global webhook URL and set the 15s timeout.

I know it is a little bit tricky but it could help you.

Also, you can automate all these things with the Dialogflow CX CLI: 

https://cxcli.xavidop.me/cmd/cxcli/

[tojagrut]

Hi @xavidop , I understand the solution.  It could be a temporary workaround as the whole purpose of environments is no longer useful with this setup.

[xavidop]

Exactly, a little bit hacky until a solution is implemented

[tojagrut · Accepted solution]

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