dify - 💡(How to fix) Fix Cannot get conversation history for workflow runs via API

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After starting a conversation via official API, we can normally fetch user conversation history through API. But when running workflows on Dify workflow preview page, or accessing embedded workflows via iframe in third-party websites, we are unable to get the corresponding conversation history via API, and there is no clear way to confirm which user ID should be passed. Bug Type: API Function Missing / Parameter Ambiguity Environment: Self-hosted Dify

curl -X POST 'http://192.168.3.123/v1/chat-messages'
-H 'Authorization: Bearer app-7lz96kRdy270HOTDnBmGWBY8'
-H 'Content-Type: application/json'
-d '{ "inputs": {}, "query": "你好,请介绍你自己", "response_mode": "blocking", "user": "my-test-user" }'

curl -X GET 'http://192.168.3.123/v1/conversations?user=my-test-user&limit=20' -H 'Authorization: Bearer app-7lz96kRdy270HOTDnBmGWBY8'

✔️ Expected Behavior

It is able to obtain all historical conversations of chatflows and workflows via API, no matter they are triggered by API calls, run directly on Dify platform, or launched via iframe embedding in third-party applications.

❌ Actual Behavior

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING