Discourse AI tool Operation timed out - FinalDestination::HTTP
How to solve the Discourse AI tool call timeout? Can the Discourse timeout be adjusted, and how?
סיכום מבוסס בינה מלאכותית
本讨论主要围绕 Discourse AI 工具调用时出现 Operation timed out - FinalDestination::HTTP 错误的问题展开。用户 shixiaochi 报告称，其通过工具接入的自建知识库检索接口因响应时间较长（20-30秒）导致超时。
管理员 Falco 指出，Discourse 当前的 read_timeout 设置为 10 秒，这是导致超时的原因。用户询问是否可以调整该超时时间。目前，官方尚未提供直接修改此设置的公开方法或隐藏配置。另一位用户 satonotdead 也反映了类似问题，表示在使用 Vane (Perplexica) 进行深度搜索时同样因超过 10 秒限制而无法运行，并建议未来能提供一个可调整的隐藏设置来解决此类长耗时 API 的兼容性问题。
Which tool are you talking about?
What is the tool!!! What is the request you are doing???
A self-built knowledge base integrated in the form of a tool. Interface for requesting knowledge base retrieval.
Our read_timeout is 10 seconds, does your API takes longer than that?
My API takes 20 to 30 seconds, are there any good solutions?
Can read_timeout be modified? How to modify it?
I am trying to use Vane (previously Perplexica — Self-hosted Perplexity alternative) and it is impossible to run it because the deep-search takes longer than 10s.
Perhaps a hidden setting can be shipped? 