dify icon indicating copy to clipboard operation
dify copied to clipboard

Store logs when a tool node runs

Open duroey opened this issue 3 months ago • 6 comments

Self Checks

  • [x] I have read the Contributing Guide and Language Policy.
  • [x] I have searched for existing issues search for existing issues, including closed ones.
  • [x] I confirm that I am using English to submit this report, otherwise it will be closed.
  • [x] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

My workflow contains some sub-workflows published as tool. When my workflow run these tool nodes, there isn't any logs on the log page of sub-workflow.

Image Image

2. Additional context or comments

The tool should store logs and show those on log page if the tool is actually a workflow

3. Can you help us with this feature?

  • [ ] I am interested in contributing to this feature.

duroey avatar Sep 11 '25 07:09 duroey

Dify currently does not store or display logs for tool nodes when the tool is a workflow. The backend runs the sub-workflow and returns its outputs, but it does not aggregate or propagate the sub-workflow's logs into the parent workflow's tool node logs. The frontend is designed to show nested logs if the backend provides them, but this linkage is missing. To support your request, backend changes are needed to collect and attach sub-workflow logs to the parent tool node's execution record, likely using metadata fields like agent_log or children so they appear in the log page as expected. The architecture supports such an extension, but it hasn't been implemented yet. See relevant code details.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

dosubot[bot] avatar Sep 11 '25 07:09 dosubot[bot]

Could you please implement the feature in next version? This is very helpful when you do modularised-development and debug for tool calls.

duroey avatar Sep 11 '25 07:09 duroey

Great suggestion

pr-maia avatar Sep 11 '25 19:09 pr-maia

Hi, @DuroyGeorge. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested that logs for tool nodes running sub-workflows be stored and displayed on the sub-workflow's log page.
  • The frontend already supports nested logs, but backend changes are required to collect and attach these sub-workflow logs to the parent tool node.
  • This backend implementation has not yet been completed.
  • You expressed interest in having this feature in the next version to improve modular development debugging.
  • A maintainer acknowledged this as a great suggestion but no further updates have been provided.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

dosubot[bot] avatar Oct 12 '25 16:10 dosubot[bot]

Yes. It's still a issue to be solved.

duroey avatar Oct 12 '25 16:10 duroey

Image

in workflow as tool execution detail, record the sub workflow log

fatelei avatar Dec 25 '25 04:12 fatelei