The logs and annotations fail to display the dialogue content

[opsvr202]

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

0.15.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1.Enter the workspace; 2. Select the app; 4. Click on the log and annotation; 5. Click on the title to display the conversation content

error pic：

✔️ Expected Behavior

display the dialogue content

❌ Actual Behavior

fail to display the dialogue content

[dosubot[bot]]

The issue you're experiencing with the logs and annotations failing to display dialogue content in Dify could be related to a few potential causes. Here are some steps and considerations that might help you troubleshoot and resolve the problem:

1. Check for TypeErrors: Since the error message mentions a TypeError related to a function call, ensure that all function parameters are correctly defined and passed. TypeErrors often occur when a function is called with incorrect argument types or missing arguments.

2. Network Requests: Verify that the network requests for retrieving conversation data are correctly configured. Ensure that the request parameters, such as conversation_id, are valid and that the API endpoints are accessible. You can refer to the typical network request parameters and JSON response structures for conversation data in Dify ^[1].

3. Error Handling: Implement error handling mechanisms for network requests. Dify supports retry strategies and error handling configurations that can help manage network request failures ^[2].

4. Recent Changes: If there have been recent updates or changes to the Dify codebase, review the commit history to identify any modifications related to logging or annotation features that might have introduced the issue.

5. Dependencies and Libraries: Ensure that all dependencies and libraries used for handling logs and annotations are up to date and compatible with your current setup.

By addressing these areas, you may be able to identify and fix the issue preventing the dialogue content from displaying correctly. If the problem persists, further investigation into the specific code handling logs and annotations might be necessary.

To continue talking to Dosu, mention @dosu.

---

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

[crazywoola]

Can you paste the error details in text?

[opsvr202]

Can you paste the error details in text?

Sorry, the data is in the intranet and cannot be accessed in the external network environment

[crazywoola]

The image you took is a little bit vague, can you take a new picture again?

[opsvr202]

The image you took is a little bit vague, can you take a new picture again?

Okay, I'll take another picture：

[lhysdl]

0.14.2 also have this problem， any solutions ？

[dosubot[bot]]

Hi, @opsvr202. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

• A bug in Dify version 0.15.0 prevents logs and annotations from displaying dialogue content in a self-hosted Docker environment.
• I suggested troubleshooting steps, including checking for TypeErrors and network requests.
• Crazywoola asked for error details, but you mentioned data is inaccessible from the external network.
• You provided clearer images of the issue, and lhysdl noted the same problem in version 0.14.2.

Next Steps:

• Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here.
• If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

[a756624802]

Check the Chromium version of your browser, too old version may cause this.