langgenius/dify-docs
1
0
Fork 0
mirror of https://github.com/langgenius/dify-docs.git synced 2026-07-22 04:15:24 -04:00
Code Issues 10 Packages Projects Releases Wiki Activity

[DOCS]: How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow. #275

New Issue
Closed
opened 2026-02-16 05:19:42 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 05:19:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @alexpadholol on GitHub (Nov 25, 2025).

Type of Documentation Change

Error/Typo fix

Documentation Page URL or Path

No response

Current Content

How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow.

Suggested Changes

How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow.

Reason for Change

How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow.

Code of Conduct

  • I agree to follow Dify's documentation contribution guidelines
  • 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.
Originally created by @alexpadholol on GitHub (Nov 25, 2025). ### Type of Documentation Change Error/Typo fix ### Documentation Page URL or Path _No response_ ### Current Content How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow. ### Suggested Changes How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow. ### Reason for Change How to build: first create a sub-process, then iteratively invoke this sub-workflow based on a list (which can originate from files or APIs), and finally consolidate the outputs of the sub-workflow. ### Code of Conduct - [x] I agree to follow Dify's documentation [contribution guidelines](https://github.com/langgenius/dify/blob/0277a37fcad5ad86aeb239485c27fffd5cd90043/CONTRIBUTING.md) - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields.
yindo added the documentation label 2026-02-16 05:19:42 -05:00
yindo closed this issue 2026-02-16 05:19:42 -05:00
yindo commented 2026-02-16 05:19:42 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 6, 2025):

Hi, @alexpadholol. I'm Dosu, and I'm helping the dify-docs team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested clarification on the workflow building process, focusing on creating sub-processes and iteratively invoking them with data from files or APIs.
  • You pointed out that the suggested documentation change repeats existing content, indicating a need for clearer or corrected explanation.
  • There has been no further activity or comments on this issue since it was opened.
  • The issue remains unresolved and no alternative solutions have been proposed.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of the dify-docs repository by commenting here.
  • If I do not hear from you within 5 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 6, 2025): Hi, @alexpadholol. I'm [Dosu](https://dosu.dev), and I'm helping the dify-docs team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested clarification on the workflow building process, focusing on creating sub-processes and iteratively invoking them with data from files or APIs. - You pointed out that the suggested documentation change repeats existing content, indicating a need for clearer or corrected explanation. - There has been no further activity or comments on this issue since it was opened. - The issue remains unresolved and no alternative solutions have been proposed. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of the dify-docs repository by commenting here. - If I do not hear from you within 5 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
documentation
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label documentation
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-docs#275
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?