Skip to content

docs: clarify workflow tool migration and verification - #1132

Draft
Mangolycheematcha wants to merge 1 commit into
langgenius:mainfrom
Mangolycheematcha:docs/workflow-tool-migration-verification
Draft

Mangolycheematcha wants to merge 1 commit into
langgenius:mainfrom
Mangolycheematcha:docs/workflow-tool-migration-verification

Conversation

@Mangolycheematcha

Copy link
Copy Markdown

In Dify 1.18.0, exporting an app that calls a workflow tool keeps the source workspace's tool reference without including the called Workflow app. The existing export/import guide lists this omission but does not explain how to reconnect the caller or verify it after migration.

Add one version-scoped section to the existing self-host guide in English, Chinese, and Japanese. It covers direct and nested dependencies, choosing a published version, preparing destination workflow tools, replacing Tool nodes and configured Agent tools, checking inputs and downstream output references, and exercising the calls before publication. It also explains the reported missing-provider error. Existing content and navigation are preserved.

Evidence and scope

Validation

  • English and CJK format checks: zero violations across the three complete pages.
  • Repository parity logic: passed, using a local Windows path-separator shim; repository tooling is unchanged.
  • Changed-page link/anchor check: passed, including navigation. Full repository check reports the same six broken anchors as an untouched main worktree; zero broken paths and zero navigation issues.
  • Mintlify local preview: all three pages rendered and visually inspected, including the four-step list and limitation callout. git diff --check passed.
  • Independent English editor and first-time reader reviews informed the final wording. The primary agent compared the translations with the frozen English. Fresh independent Chinese/Japanese judges could not run because Luna hit its usage limit; maintainer language review remains pending.
  • Product guidance was validated against pinned source, not an end-to-end migration between running Dify workspaces. Keep this PR as a draft pending that validation and language review.

From Codex

@mintlify

mintlify Bot commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit bce65e6.

Approve preview

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant