Webhook call failed. Error: DEADLINE_EXCEEDED | Request timed out
Webhook call failed. Error: DEADLINE_EXCEEDED | Request timed out
我正在使用 ASP.Net 作为后端 webhook。一些请求已成功执行，很少有人收到此错误：
Webhook call failed. Error: DEADLINE_EXCEEDED
但是当我添加一个稍微大一点的操作时，它至少需要 2 秒才能完成并在大约 3 秒内做出响应，我不断收到此错误。
我认为问题只是请求超时。我无法加快响应速度，因为它在 2-3 个第 3 方服务器之间路由。所以在某种程度上，我需要增加我的机器人在对话流中的响应等待时间。
恐怕这不可能，您可以解决实现异步后台线程的问题
这是我从 Dialogflow 支持收到的信息。
Hi,
Thanks for reaching out to Dialogflow Support. Webhook timeout limit
for Actions on Google integration is 10 seconds. For all other
integrations, including self-developed implementations sending
requests to our API, webhook timeout is 5 seconds. These values are
not customizable. The timeout limit includes time for Dialogflow
requests to your webhook endpoint, the webhook processing time, and
webhook response time back to Dialogflow.
Conversational interfaces are meant to be designed as a continuous
message exchange between the end user and the app/bot. If your web
service requires more time for executing operations in the background
and this cannot be optimized, consider redesigning the conversation
flow in such way that end users don't wait for the app/bot reply for
more than 5 seconds (10 for Actions on Google).
Let me know if you have any questions.
Regards, Mark Dialogflow Support Team
所以唯一的选择是在您收到来自 webhook 的响应时让用户保持对话
我正在使用 ASP.Net 作为后端 webhook。一些请求已成功执行，很少有人收到此错误：
Webhook call failed. Error: DEADLINE_EXCEEDED
但是当我添加一个稍微大一点的操作时，它至少需要 2 秒才能完成并在大约 3 秒内做出响应，我不断收到此错误。
我认为问题只是请求超时。我无法加快响应速度，因为它在 2-3 个第 3 方服务器之间路由。所以在某种程度上，我需要增加我的机器人在对话流中的响应等待时间。
恐怕这不可能，您可以解决实现异步后台线程的问题
这是我从 Dialogflow 支持收到的信息。
Hi,
Thanks for reaching out to Dialogflow Support. Webhook timeout limit for Actions on Google integration is 10 seconds. For all other integrations, including self-developed implementations sending requests to our API, webhook timeout is 5 seconds. These values are not customizable. The timeout limit includes time for Dialogflow requests to your webhook endpoint, the webhook processing time, and webhook response time back to Dialogflow.
Conversational interfaces are meant to be designed as a continuous message exchange between the end user and the app/bot. If your web service requires more time for executing operations in the background and this cannot be optimized, consider redesigning the conversation flow in such way that end users don't wait for the app/bot reply for more than 5 seconds (10 for Actions on Google).
Let me know if you have any questions.
Regards, Mark Dialogflow Support Team
所以唯一的选择是在您收到来自 webhook 的响应时让用户保持对话