Arize lack message in traces tab

[runzhezhang11]

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.7.2 / Enterprise v3.4.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

We have accessed arize for tracing successful.But there is no message in traced tab, but only exist in span.

✔️ Expected Behavior

We can find traces in the tab

❌ Actual Behavior

No response

[dosubot]

This is a known issue in Dify's tracing UI: the frontend expects every message to be part of a strict question/answer pair. If your conversation has an odd number of messages or any orphaned messages, the tracing panel in the UI can silently fail and not display trace details—even though spans are visible and tracing is working at the backend. This limitation has been reported in recent versions and is not specific to Arize, but affects all tracing providers integrated in this way [source].

As a workaround, check that your conversations have even numbers of question/answer pairs and no orphaned messages. If you have database access, look for incomplete or mismatched message pairs and correct them. This should restore trace visibility in the traced tab.

There is also a backend guard clause in the Arize/Phoenix integration that skips traces if message_data is None, which can result in missing trace messages in the traced tab while spans are still visible. A fix for this logic has been proposed and may be included in future releases [source].

If you continue to have issues, review your tracing provider configuration and environment variables, and consider upgrading to the latest Dify version, as some UI and backend bugs have been fixed in newer releases [source].

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}