tts_message sometimes fails to return

[xueyezs]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When calling the intelligent agent API, tts_message sometimes fails to return, and after testing, it has been confirmed that this is an accidental error.

✔️ Expected Behavior

Stable return of tts_message.

❌ Actual Behavior

tts_message sometimes fails to return

[dosubot[bot]]

The issue you're experiencing with tts_message sometimes failing to return could be related to error handling mechanisms in the Dify codebase. When exceptions occur during the streaming process, they are output as stream events, and an error event will end the stream. This error event includes details such as task_id, message_id, status, code, and message ^[1][2].

To troubleshoot this issue, you might want to check the error events being logged when tts_message fails to return. This can provide insights into what might be causing the failure. Additionally, ensure that all dependencies and configurations, such as FFmpeg installation and middleware setup, are correctly implemented in your self-hosted Docker environment ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[charli117]

tts_message will return only when auto-play is enabled in the application. Make sure that voice auto-play is enabled in your application

[xueyezs]

您遇到的有时无法返回的问题可能与 Dify 代码库中的错误处理机制有关。推流过程中出现异常时，会作为 stream events 输出，Error 事件会结束 stream。此错误事件包括 、 和tts_message``task_id``message_id``status``code``message [1][2].

要解决此问题，您可能需要检查在无法返回时记录的错误事件。这可以深入了解可能导致失败的原因。此外，请确保所有依赖项和配置（例如 FFmpeg 安装和中间件设置）都在自托管 Docker 环境中正确实现tts_message[3].

要继续与 Dosu 交谈，请提及 。

帮助 Dosu 学习！给它反馈：伟大的回应 |无关紧要的答案 |不正确的来源 |太冗长 |幻觉 |Bug 报告 |其他

When I call the API, the same application has the same settings, but it often does not return tts_message

[xueyezs]

您遇到的有时无法返回的问题可能与 Dify 代码库中的错误处理机制有关。推流过程中出现异常时，会作为 stream events 输出，Error 事件会结束 stream。此错误事件包括 、 和tts_message``task_id``message_id``status``code``message [1][2].

要解决此问题，您可能需要检查在无法返回时记录的错误事件。这可以深入了解可能导致失败的原因。此外，请确保所有依赖项和配置（例如 FFmpeg 安装和中间件设置）都在自托管 Docker 环境中正确实现tts_message[3].

要继续与 Dosu 交谈，请提及 。

帮助 Dosu 学习！给它反馈：伟大的回应 |无关紧要的答案 |不正确的来源 |太冗长 |幻觉 |Bug 报告 |其他

I have identified the cause of the problem. If the large model returns fewer words, there is a high probability that tts_message will not be returned. If the word count is longer, tts_message can still be returned normally.

[charli117]

tts_message will only appear after auto play is turned on. In addition, first eliminate the service anomalies of the tts model, and then select a relatively stable tts model for verification