langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-19 16:44:00 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #27937] fix(api): Trace Hierarchy, Span Status, and Broken Workflow for Arize & Phoenix Integration #31901

New Issue
Closed
opened 2026-02-21 20:50:21 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:50:21 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/27937

State: closed
Merged: Yes

Summary

This PR resolves the issues regarding trace hierarchy, span status, and broken workflow trace / missing node spans in the Arize & Phoenix integration, ensuring spans are correctly linked to their parents and accurately reflect execution outcomes. It restores proper trace relationships and improves observability across Dify apps.

Screenshots

Before

Dify_Trace_New

After

Dify_Trace_Update - Dify_Trace_Workflow

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Closes https://github.com/langgenius/dify/issues/26304
Closes https://github.com/langgenius/dify/issues/26294

**Original Pull Request:** https://github.com/langgenius/dify/pull/27937 **State:** closed **Merged:** Yes --- ## Summary This PR resolves the issues regarding trace hierarchy, span status, and broken workflow trace / missing node spans in the Arize & Phoenix integration, ensuring spans are correctly linked to their parents and accurately reflect execution outcomes. It restores proper trace relationships and improves observability across Dify apps. ## Screenshots **Before** <img width="1920" height="977" alt="Dify_Trace_New" src="https://github.com/user-attachments/assets/b3b37b4a-15f8-4075-b3f6-62db9a5ea85a" /> **After** <img width="1920" height="976" alt="Dify_Trace_Update" src="https://github.com/user-attachments/assets/b1e61bd2-4786-4ace-8177-7354419919dd" /> - <img width="1920" height="976" alt="Dify_Trace_Workflow" src="https://github.com/user-attachments/assets/afadf106-b2b9-4eee-b1a0-de4eaf6cc2f6" /> ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [ ] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods Closes https://github.com/langgenius/dify/issues/26304 Closes https://github.com/langgenius/dify/issues/26294
yindo added the pull-request label 2026-02-21 20:50:21 -05:00
yindo closed this issue 2026-02-21 20:50:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#31901
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?