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

workflow as tool call return plugin not found error #22098

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

Originally created by @fatelei on GitHub (Feb 5, 2026).

Originally assigned to: @zxhlyh on GitHub.

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.12.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. publish workflow as tool
  2. call workflow tool in chatflow
  3. error return plugin not found
Image 
Traceback (most recent call last):
  File "/Users/fatelei/dify/dify/api/core/workflow/nodes/base/node.py", line 332, in run
    for event in result:
                 ^^^^^^
  File "/Users/fatelei/dify/dify/api/core/workflow/nodes/agent/agent_node.py", line 102, in _run
    parameters = self._generate_agent_parameters(
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/workflow/nodes/agent/agent_node.py", line 286, in _generate_agent_parameters
    tool_runtime = ToolManager.get_agent_tool_runtime(
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 369, in get_agent_tool_runtime
    tool_entity = cls.get_tool_runtime(
                  ^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 185, in get_tool_runtime
    provider_controller = cls.get_builtin_provider(provider_id, tenant_id)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 114, in get_builtin_provider
    plugin_provider = cls.get_plugin_provider(provider, tenant_id)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 144, in get_plugin_provider
    provider_entity = manager.fetch_tool_provider(tenant_id, provider)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/plugin/impl/tool.py", line 67, in fetch_tool_provider
    response = self._request_with_plugin_daemon_response(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/fatelei/dify/dify/api/core/plugin/impl/base.py", line 264, in _request_with_plugin_daemon_response
    self._handle_plugin_daemon_error(error.error_type, error.message)
  File "/Users/fatelei/dify/dify/api/core/plugin/impl/base.py", line 357, in _handle_plugin_daemon_error
    raise PluginNotFoundError(description=message)
core.plugin.impl.exc.PluginNotFoundError: req_id: 8f4aeba96f PluginNotFoundError: plugin not found

✔️ Expected Behavior

no error

❌ Actual Behavior

error return plugin not found

Originally created by @fatelei on GitHub (Feb 5, 2026). Originally assigned to: @zxhlyh on GitHub. ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.12.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. publish workflow as tool 2. call workflow tool in chatflow 3. error return plugin not found <img width="3840" height="1986" alt="Image" src="https://github.com/user-attachments/assets/5da1fe41-7b3a-4241-b8f5-453dc787e788" /> ``` Traceback (most recent call last): File "/Users/fatelei/dify/dify/api/core/workflow/nodes/base/node.py", line 332, in run for event in result: ^^^^^^ File "/Users/fatelei/dify/dify/api/core/workflow/nodes/agent/agent_node.py", line 102, in _run parameters = self._generate_agent_parameters( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/workflow/nodes/agent/agent_node.py", line 286, in _generate_agent_parameters tool_runtime = ToolManager.get_agent_tool_runtime( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 369, in get_agent_tool_runtime tool_entity = cls.get_tool_runtime( ^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 185, in get_tool_runtime provider_controller = cls.get_builtin_provider(provider_id, tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 114, in get_builtin_provider plugin_provider = cls.get_plugin_provider(provider, tenant_id) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/tools/tool_manager.py", line 144, in get_plugin_provider provider_entity = manager.fetch_tool_provider(tenant_id, provider) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/plugin/impl/tool.py", line 67, in fetch_tool_provider response = self._request_with_plugin_daemon_response( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Users/fatelei/dify/dify/api/core/plugin/impl/base.py", line 264, in _request_with_plugin_daemon_response self._handle_plugin_daemon_error(error.error_type, error.message) File "/Users/fatelei/dify/dify/api/core/plugin/impl/base.py", line 357, in _handle_plugin_daemon_error raise PluginNotFoundError(description=message) core.plugin.impl.exc.PluginNotFoundError: req_id: 8f4aeba96f PluginNotFoundError: plugin not found ``` ### ✔️ Expected Behavior no error ### ❌ Actual Behavior error return plugin not found
yindo added the 🐞 bug label 2026-02-21 20:15:46 -05:00
yindo closed this issue 2026-02-21 20:15:46 -05:00
yindo commented 2026-02-21 20:15:46 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 5, 2026):

The "plugin not found" error when calling a workflow published as a tool usually means Dify can't find the workflow tool provider or its registration in the database at runtime. This is often due to issues with tool registration, Docker environment config, or service startup order in self-hosted setups.

Here's how the workflow-as-tool mechanism works: when you publish a workflow as a tool, Dify creates a WorkflowToolProvider record in the database. At runtime, ToolManager looks up this provider by tenant and provider ID. If it can't find the provider or the tool, it raises a ToolProviderNotFoundError, which surfaces as the "plugin not found" error you see. This can happen if the provider record is missing, the Docker environment is misconfigured, or required environment variables (like CONSOLE_API_URL) are unset or incorrect, which can break tool discovery and icon/metadata URLs [code reference].

To troubleshoot:

  1. Make sure the workflow tool provider exists in the database (table tool_workflow_providers) and matches your tenant and app.
  2. Check that all Docker containers are running and healthy, and that they are on the same network.
  3. Verify your .env file has the correct CONSOLE_API_URL (and restart containers after changes).
  4. If you recently published the workflow as a tool, try restarting the API and worker containers to clear any stale cache.
  5. Enable debug logging (LOG_LEVEL=DEBUG) and check logs for more detailed error messages.

If the tool name in your agent node doesn't exactly match the registered tool's name (case and spacing included), the call may also fail [related issue].

If you still see the error after these checks, there may be a deeper issue with tool registration or a bug in this Dify version. Upgrading to a newer release (if available) may help, as there have been ongoing improvements and bugfixes in workflow tool handling.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 5, 2026): <!-- Answer --> The "plugin not found" error when calling a workflow published as a tool usually means Dify can't find the workflow tool provider or its registration in the database at runtime. This is often due to issues with tool registration, Docker environment config, or service startup order in self-hosted setups. Here's how the workflow-as-tool mechanism works: when you publish a workflow as a tool, Dify creates a WorkflowToolProvider record in the database. At runtime, ToolManager looks up this provider by tenant and provider ID. If it can't find the provider or the tool, it raises a ToolProviderNotFoundError, which surfaces as the "plugin not found" error you see. This can happen if the provider record is missing, the Docker environment is misconfigured, or required environment variables (like `CONSOLE_API_URL`) are unset or incorrect, which can break tool discovery and icon/metadata URLs [[code reference](https://github.com/langgenius/dify/blob/7202a24bcf1a9aa02e9d5f5e419ff44e7d7d99a4/api/core/tools/tool_manager.py#L75-L439)]. To troubleshoot: 1. Make sure the workflow tool provider exists in the database (table `tool_workflow_providers`) and matches your tenant and app. 2. Check that all Docker containers are running and healthy, and that they are on the same network. 3. Verify your `.env` file has the correct `CONSOLE_API_URL` (and restart containers after changes). 4. If you recently published the workflow as a tool, try restarting the API and worker containers to clear any stale cache. 5. Enable debug logging (`LOG_LEVEL=DEBUG`) and check logs for more detailed error messages. If the tool name in your agent node doesn't exactly match the registered tool's name (case and spacing included), the call may also fail [[related issue](https://github.com/langgenius/dify-official-plugins/issues/2375)]. If you still see the error after these checks, there may be a deeper issue with tool registration or a bug in this Dify version. Upgrading to a newer release (if available) may help, as there have been ongoing improvements and bugfixes in workflow tool handling. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9050335c-2c71-48ff-924f-5c54a4b710cf?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22plugin%20not%20found%22%20error%20when%20calling%20a%20workflow%20published%20as%20a%20tool%20usually%20means%20Dify%20can%27t%20find%20the%20workflow%20tool%20provider%20or%20its%20registration%20in%20the%20database%20at%20runtime.%20This%20is%20often%20due%20to%20issues%20with%20tool%20registration%2C%20Docker%20environment%20config%2C%20or%20service%20startup%20order%20in%20self-hosted%20setups.%0A%0AHere%27s%20how%20the%20workflow-as-tool%20mechanism%20works%3A%20when%20you%20publish%20a%20workflow%20as%20a%20tool%2C%20Dify%20creates%20a%20WorkflowToolProvider%20record%20in%20the%20database.%20At%20runtime%2C%20ToolManager%20looks%20up%20this%20provider%20by%20tenant%20and%20provider%20ID.%20If%20it%20can%27t%20find%20the%20provider%20or%20the%20tool%2C%20it%20raises%20a%20ToolProviderNotFoundError%2C%20which%20surfaces%20as%20the%20%22plugin%20not%20found%22%20error%20you%20see.%20This%20can%20happen%20if%20the%20provider%20record%20is%20missing%2C%20the%20Docker%20environment%20is%20misconfigured%2C%20or%20required%20environment%20variables%20%28like%20%60CONSOLE_API_URL%60%29%20are%20unset%20or%20incorrect%2C%20which%20can%20break%20tool%20discovery%20and%20icon/metadata%20URLs%20%5B%5Bcode%20reference%5D%28https%3A//github.com/langgenius/dify/blob/7202a24bcf1a9aa02e9d5f5e419ff44e7d7d99a4/api/core/tools/tool_manager.py%23L75-L439%29%5D.%0A%0ATo%20troubleshoot%3A%0A%0A1.%20Make%20sure%20the%20workflow%20tool%20provider%20exists%20in%20the%20database%20%28table%20%60tool_workflow_providers%60%29%20and%20matches%20your%20tenant%20and%20app.%0A2.%20Check%20that%20all%20Docker%20containers%20are%20running%20and%20healthy%2C%20and%20that%20they%20are%20on%20the%20same%20network.%0A3.%20Verify%20your%20%60.env%60%20file%20has%20the%20correct%20%60CONSOLE_API_URL%60%20%28and%20restart%20containers%20after%20changes%29.%0A4.%20If%20you%20recently%20published%20the%20workflow%20as%20a%20tool%2C%20try%20restarting%20the%20API%20and%20worker%20containers%20to%20clear%20any%20stale%20cache.%0A5.%20Enable%20debug%20logging%20%28%60LOG_LEVEL%3DDEBUG%60%29%20and%20check%20logs%20for%20more%20detailed%20error%20messages.%0A%0AIf%20the%20tool%20name%20in%20your%20agent%20node%20doesn%27t%20exactly%20match%20the%20registered%20tool%27s%20name%20%28case%20and%20spacing%20included%29%2C%20the%20call%20may%20also%20fail%20%5B%5Brelated%20issue%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2375%29%5D.%0A%0AIf%20you%20still%20see%20the%20error%20after%20these%20checks%2C%20there%20may%20be%20a%20deeper%20issue%20with%20tool%20registration%20or%20a%20bug%20in%20this%20Dify%20version.%20Upgrading%20to%20a%20newer%20release%20%28if%20available%29%20may%20help%2C%20as%20there%20have%20been%20ongoing%20improvements%20and%20bugfixes%20in%20workflow%20tool%20handling.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/32005)
yindo commented 2026-02-21 20:15:46 -05:00
Author
Owner
Copy Link
Copy Source

@lgbo-ustc commented on GitHub (Feb 5, 2026):

Encountering the same issue on the agent node

2026/02/06 02:34:56 /app/internal/db/executor.go:259 record not found
[0.365ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = 'd69e3016-a19c-44ef-b954-5b2c23a84635' AND plugin_id = 'xxxx "tool_installations"."id" LIMIT 1
@lgbo-ustc commented on GitHub (Feb 5, 2026): Encountering the same issue on the agent node ``` 2026/02/06 02:34:56 /app/internal/db/executor.go:259 record not found [0.365ms] [rows:0] SELECT * FROM "tool_installations" WHERE tenant_id = 'd69e3016-a19c-44ef-b954-5b2c23a84635' AND plugin_id = 'xxxx "tool_installations"."id" LIMIT 1 ```
yindo commented 2026-02-21 20:15:46 -05:00
Author
Owner
Copy Link
Copy Source

@QuantumGhost commented on GitHub (Feb 5, 2026):

The PR #32008 mitigates this issue but does not fully resolve it.

I have created a workflow with the following structure:

Image

The key path (in JSONPath) .workflow.graph.nodes[2].data.agent_parameters.tools.value[0].provider_type does not exist.

DSL: 
app:
  description: ''
  icon: 🤖
  icon_background: '#FFEAD5'
  mode: advanced-chat
  name: test-agent-tool
  use_icon_as_answer_icon: false
dependencies: []
kind: app
version: 0.5.0
workflow:
  conversation_variables: []
  environment_variables: []
  features:
    file_upload:
      allowed_file_extensions:
      - .JPG
      - .JPEG
      - .PNG
      - .GIF
      - .WEBP
      - .SVG
      allowed_file_types:
      - image
      allowed_file_upload_methods:
      - local_file
      - remote_url
      enabled: false
      fileUploadConfig:
        attachment_image_file_size_limit: 2
        audio_file_size_limit: 50
        batch_count_limit: 5
        file_size_limit: 15
        file_upload_limit: 50
        image_file_batch_limit: 10
        image_file_size_limit: 10
        single_chunk_attachment_limit: 10
        video_file_size_limit: 100
        workflow_file_upload_limit: 10
      image:
        enabled: false
        number_limits: 3
        transfer_methods:
        - local_file
        - remote_url
      number_limits: 3
    opening_statement: ''
    retriever_resource:
      enabled: true
    sensitive_word_avoidance:
      enabled: false
    speech_to_text:
      enabled: false
    suggested_questions: []
    suggested_questions_after_answer:
      enabled: false
    text_to_speech:
      enabled: false
      language: ''
      voice: ''
  graph:
    edges:
    - data:
        isInIteration: false
        isInLoop: false
        sourceType: start
        targetType: agent
      id: 1770348482009-source-1770348488484-target
      source: '1770348482009'
      sourceHandle: source
      target: '1770348488484'
      targetHandle: target
      type: custom
      zIndex: 0
    - data:
        isInLoop: false
        sourceType: agent
        targetType: answer
      id: 1770348488484-source-answer-target
      source: '1770348488484'
      sourceHandle: source
      target: answer
      targetHandle: target
      type: custom
      zIndex: 0
    nodes:
    - data:
        selected: false
        title: User Input
        type: start
        variables: []
      height: 73
      id: '1770348482009'
      position:
        x: 80
        y: 282
      positionAbsolute:
        x: 80
        y: 282
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 242
    - data:
        answer: '{{#1770348488484.text#}}'
        selected: false
        title: Answer
        type: answer
        variables: []
      height: 103
      id: answer
      position:
        x: 900
        y: 282
      positionAbsolute:
        x: 900
        y: 282
      selected: false
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 242
    - data:
        agent_parameters:
          instruction:
            type: constant
            value: 请生成诗句
          model:
            type: constant
            value:
              completion_params: {}
              mode: chat
              model: gpt-4o
              model_type: llm
              provider: langgenius/openai/openai
              type: model-selector
          tools:
            type: constant
            value:
            - enabled: true
              extra:
                description: Poem Generator
              parameters:
                count:
                  auto: 1
                  value: null
                query:
                  auto: 1
                  value: null
                subject:
                  auto: 1
                  value: null
              provider_name: 6226b87f-51b6-4cfc-b7e0-a87038834d55
              provider_show_name: PoemGenerator
              settings: {}
              tool_description: Poem Generator
              tool_label: PoemGenerator
              tool_name: poem_generator
        agent_strategy_label: FunctionCalling
        agent_strategy_name: function_calling
        agent_strategy_provider_name: langgenius/agent/agent
        meta:
          minimum_dify_version: 1.7.0
          version: 0.0.2
        output_schema: {}
        plugin_unique_identifier: langgenius/agent:0.0.31@faea70b63e46a8d42f060bd005cfbc8af8e229b3b7f2b8ed253669efef42846a
        selected: false
        title: Agent
        tool_node_version: '2'
        type: agent
      height: 188
      id: '1770348488484'
      position:
        x: 382
        y: 282
      positionAbsolute:
        x: 382
        y: 282
      selected: true
      sourcePosition: right
      targetPosition: left
      type: custom
      width: 242
    viewport:
      x: 0
      y: 1
      zoom: 1
  rag_pipeline_variables: []
@QuantumGhost commented on GitHub (Feb 5, 2026): The PR #32008 mitigates this issue but does not fully resolve it. I have created a workflow with the following structure: <img width="1002" height="321" alt="Image" src="https://github.com/user-attachments/assets/f2f7716f-9015-4e45-8ba4-d2c144e1cce6" /> The key path (in JSONPath) `.workflow.graph.nodes[2].data.agent_parameters.tools.value[0].provider_type` does not exist. <details> <summary>DSL:</summary> ```yaml app: description: '' icon: 🤖 icon_background: '#FFEAD5' mode: advanced-chat name: test-agent-tool use_icon_as_answer_icon: false dependencies: [] kind: app version: 0.5.0 workflow: conversation_variables: [] environment_variables: [] features: file_upload: allowed_file_extensions: - .JPG - .JPEG - .PNG - .GIF - .WEBP - .SVG allowed_file_types: - image allowed_file_upload_methods: - local_file - remote_url enabled: false fileUploadConfig: attachment_image_file_size_limit: 2 audio_file_size_limit: 50 batch_count_limit: 5 file_size_limit: 15 file_upload_limit: 50 image_file_batch_limit: 10 image_file_size_limit: 10 single_chunk_attachment_limit: 10 video_file_size_limit: 100 workflow_file_upload_limit: 10 image: enabled: false number_limits: 3 transfer_methods: - local_file - remote_url number_limits: 3 opening_statement: '' retriever_resource: enabled: true sensitive_word_avoidance: enabled: false speech_to_text: enabled: false suggested_questions: [] suggested_questions_after_answer: enabled: false text_to_speech: enabled: false language: '' voice: '' graph: edges: - data: isInIteration: false isInLoop: false sourceType: start targetType: agent id: 1770348482009-source-1770348488484-target source: '1770348482009' sourceHandle: source target: '1770348488484' targetHandle: target type: custom zIndex: 0 - data: isInLoop: false sourceType: agent targetType: answer id: 1770348488484-source-answer-target source: '1770348488484' sourceHandle: source target: answer targetHandle: target type: custom zIndex: 0 nodes: - data: selected: false title: User Input type: start variables: [] height: 73 id: '1770348482009' position: x: 80 y: 282 positionAbsolute: x: 80 y: 282 sourcePosition: right targetPosition: left type: custom width: 242 - data: answer: '{{#1770348488484.text#}}' selected: false title: Answer type: answer variables: [] height: 103 id: answer position: x: 900 y: 282 positionAbsolute: x: 900 y: 282 selected: false sourcePosition: right targetPosition: left type: custom width: 242 - data: agent_parameters: instruction: type: constant value: 请生成诗句 model: type: constant value: completion_params: {} mode: chat model: gpt-4o model_type: llm provider: langgenius/openai/openai type: model-selector tools: type: constant value: - enabled: true extra: description: Poem Generator parameters: count: auto: 1 value: null query: auto: 1 value: null subject: auto: 1 value: null provider_name: 6226b87f-51b6-4cfc-b7e0-a87038834d55 provider_show_name: PoemGenerator settings: {} tool_description: Poem Generator tool_label: PoemGenerator tool_name: poem_generator agent_strategy_label: FunctionCalling agent_strategy_name: function_calling agent_strategy_provider_name: langgenius/agent/agent meta: minimum_dify_version: 1.7.0 version: 0.0.2 output_schema: {} plugin_unique_identifier: langgenius/agent:0.0.31@faea70b63e46a8d42f060bd005cfbc8af8e229b3b7f2b8ed253669efef42846a selected: false title: Agent tool_node_version: '2' type: agent height: 188 id: '1770348488484' position: x: 382 y: 282 positionAbsolute: x: 382 y: 282 selected: true sourcePosition: right targetPosition: left type: custom width: 242 viewport: x: 0 y: 1 zoom: 1 rag_pipeline_variables: [] ``` </details>
yindo commented 2026-02-21 20:15:47 -05:00
Author
Owner
Copy Link
Copy Source

@imchatkit commented on GitHub (Feb 6, 2026):

I also encountered the same problem as yours. It was working fine in the morning, but started giving this error in the afternoon.

@imchatkit commented on GitHub (Feb 6, 2026): I also encountered the same problem as yours. It was working fine in the morning, but started giving this error in the afternoon.
yindo commented 2026-02-21 20:15:47 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Feb 6, 2026):

I also encountered the same problem as yours. It was working fine in the morning, but started giving this error in the afternoon.

the latest code has fix it, this a frontend issue

@fatelei commented on GitHub (Feb 6, 2026): > I also encountered the same problem as yours. It was working fine in the morning, but started giving this error in the afternoon. the latest code has fix it, this a frontend issue
yindo commented 2026-02-21 20:15:47 -05:00
Author
Owner
Copy Link
Copy Source

@imchatkit commented on GitHub (Feb 6, 2026):

我也遇到了和你一样的问题。早上还好好的，下午就开始出现这个错误了。

最新代码已经修复了这个问题，这是前端问题。

i use dify cloud version . this my bug :
https://github.com/langgenius/dify/issues/32048

@imchatkit commented on GitHub (Feb 6, 2026): > > 我也遇到了和你一样的问题。早上还好好的，下午就开始出现这个错误了。 > > 最新代码已经修复了这个问题，这是前端问题。 i use dify cloud version . this my bug : https://github.com/langgenius/dify/issues/32048
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 🐞 bug
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#22098
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?