The Interface For Obtaining Session History Messages Reports An Error

by ADMIN 70 views

Introduction

As a user of the Dify platform, we strive to provide a seamless experience for our users. However, we have encountered an issue that requires attention. After upgrading from version 0.5.3 to 1.2.0, the interface for obtaining session history messages reports an error. This error occurs when attempting to retrieve session history messages using the provided API endpoint. In this article, we will delve into the details of this issue and provide a step-by-step guide on how to reproduce it.

Self Checks

Before submitting this bug report, we have conducted a thorough self-check to ensure that we have followed the proper procedures.

  • This is only for bug report: We understand that this is a bug report and not a question. If you would like to ask a question, please head to the Discussions section.
  • Searched for existing issues: We have searched for existing issues, including closed ones, to ensure that this issue has not been reported before. You can find the search results here.
  • Confirmed English submission: We confirm that we are using English to submit this report and have read and agreed to the Language Policy.
  • Please do not modify this template: We have not modified this template and have filled in all the required fields.

Dify Version

We are currently using version 1.2.0 of the Dify platform.

Cloud or Self Hosted

Our Dify instance is self-hosted using Docker.

Steps to Reproduce

To reproduce this issue, follow these steps:

  1. Upgrade to version 1.2.0: Upgrade your Dify instance from version 0.5.3 to 1.2.0.

  2. Use the API endpoint: Use the following API endpoint to retrieve session history messages:

curl -X GET 'http://xxx.xxx.xxx/v1/messages?conversation_id=9b94fef9-f2ff-4b9f-b918-950225ffbf73&user=18998808500' --header 'Authorization: Bearer app-a8ndbiA1qn8hFZHc3OQ5uoGv'


    Replace `xxx.xxx.xxx` with your actual instance URL.

3.  **Observe the error**: Observe the error message returned by the API endpoint. The error message should be:

    ```json
{"message": "Internal Server Error", "code": "unknown"}

Expected Behavior

The expected behavior is that the API endpoint should return the session history messages without any errors.

Actual Behavior

The actual behavior is that the API endpoint returns an internal server error with a code of "unknown".

Conclusion

In conclusion, we have reported an issue with the interface for obtaining session history messages in version 1.2.0 of the Dify platform. The issue occurs when attempting to retrieve session history messages using the provided API endpoint. We have provided a step-by-step guide on to reproduce this issue and have confirmed that we have followed the proper procedures. We hope that this issue will be addressed promptly to ensure a seamless experience for our users.

Additional Information

If you have any additional information or would like to provide more context, please feel free to do so. We appreciate your help in resolving this issue.

Related Issues

If you have encountered similar issues or have any related questions, please feel free to ask in the Discussions section.

Acknowledgement

We would like to acknowledge the efforts of the Dify team in providing a robust and reliable platform. We appreciate their dedication to resolving issues and improving the user experience.

References

  • Dify Documentation
  • Dify Issues
  • Language Policy
    Frequently Asked Questions (FAQs) - The Interface for Obtaining Session History Messages Reports an Error =====================================================================================================

Q: What is the issue with the interface for obtaining session history messages?

A: The issue is that the interface for obtaining session history messages reports an error when attempting to retrieve session history messages using the provided API endpoint. The error message is an internal server error with a code of "unknown".

Q: What is the expected behavior?

A: The expected behavior is that the API endpoint should return the session history messages without any errors.

Q: What is the actual behavior?

A: The actual behavior is that the API endpoint returns an internal server error with a code of "unknown".

Q: How can I reproduce the issue?

A: To reproduce the issue, follow these steps:

  1. Upgrade to version 1.2.0: Upgrade your Dify instance from version 0.5.3 to 1.2.0.

  2. Use the API endpoint: Use the following API endpoint to retrieve session history messages:

curl -X GET 'http://xxx.xxx.xxx/v1/messages?conversation_id=9b94fef9-f2ff-4b9f-b918-950225ffbf73&user=18998808500' --header 'Authorization: Bearer app-a8ndbiA1qn8hFZHc3OQ5uoGv'


    Replace `xxx.xxx.xxx` with your actual instance URL.
3.  **Observe the error**: Observe the error message returned by the API endpoint. The error message should be:

    ```json
{"message": "Internal Server Error", "code": "unknown"}

Q: What are the system requirements for this issue?

A: The system requirements for this issue are:

  • Dify version: Version 1.2.0
  • Cloud or Self Hosted: Self-hosted using Docker

Q: How can I report this issue?

A: To report this issue, please follow these steps:

  1. Search for existing issues: Search for existing issues, including closed ones, to ensure that this issue has not been reported before.
  2. Submit a new issue: Submit a new issue using the Dify Issues template.
  3. Provide detailed information: Provide detailed information about the issue, including the steps to reproduce it and any relevant error messages.

Q: What is the estimated time for resolution?

A: The estimated time for resolution is not specified. However, we will do our best to resolve this issue as soon as possible.

Q: How can I stay updated on the status of this issue?

A: To stay updated on the status of this issue, please follow these steps:

  1. Subscribe to the issue: Subscribe to the issue using the Dify Issues template.
  2. Check the issue regularly: Check the issue regularly for updates on the status of the issue.
  3. Contact the Dify team: Contact the D team using the Dify Discussions section if you have any questions or concerns.

Q: What are the next steps?

A: The next steps are:

  1. Investigate the issue: Investigate the issue to determine the root cause of the problem.
  2. Develop a solution: Develop a solution to fix the issue.
  3. Test the solution: Test the solution to ensure that it works as expected.
  4. Deploy the solution: Deploy the solution to the production environment.

Q: What is the expected outcome?

A: The expected outcome is that the issue will be resolved and the interface for obtaining session history messages will work as expected.