Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The chart of average interaction counts per conversation show nothing #11862

Closed
5 tasks done
leslie2046 opened this issue Dec 20, 2024 · 1 comment · Fixed by #12199
Closed
5 tasks done

The chart of average interaction counts per conversation show nothing #11862

leslie2046 opened this issue Dec 20, 2024 · 1 comment · Fixed by #12199
Labels
🐞 bug Something isn't working

Comments

@leslie2046
Copy link
Contributor

leslie2046 commented Dec 20, 2024

Self Checks

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

Dify version

0.14.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

The chart of average conversation interaction for chat type apps is not displayed, but it is displayed for agents
a0afd811d7c4aca40af8ec4471820da

✔️ Expected Behavior

correctly display

❌ Actual Behavior

no data in response from backend

Copy link

dosubot bot commented Dec 20, 2024

The issue you're experiencing with the chart of average interaction counts per conversation not displaying data could be related to the API returning an empty data array. One known reason for receiving an empty data array in the JSON response is when using a multimodal model with a File type custom field, which can cause the LLM Node to return an empty array [1].

Additionally, ensure that the API endpoint /apps/<uuid:app_id>/statistics/average-session-interactions is correctly set up and that the SQL query logic is functioning as expected. This endpoint requires proper authentication, and the SQL query filters data based on the app_id and optional start and end date-time parameters [2].

Check if there are any specific conditions or filters applied in your setup that might result in an empty data array. Also, verify that the data exists for the specified time range and app ID. If the issue persists, reviewing the backend logic and any console warnings related to CSS properties or API requests might provide further insights.

To continue talking to Dosu, mention @dosu.


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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant