mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
The comfyui plugin is not fully compatible with 1.12.1. #964
Reference in New Issue
Block a user
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?
Originally created by @bright141 on GitHub (Feb 7, 2026).
Self Checks
Dify version
1.12.1
Plugin version
0.3.3
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
When this plugin's workflow is released as a tool, if another workflow executes this tool, the following error will occur. However, the workflow where the tool is located works normally. The problem might be related to the names of the file variables.
The problem emerged when upgrading from version 1.11.4 to 1.12.1.
✔️ Error log
{
"error_message": "1 validation error for FileMessage\n Value error, Invalid FileMessage: missing file_marker [type=value_error, input_value={}, input_type=dict]\n For further information visit https://errors.pydantic.dev/2.11/v/value_error",
"error_type": "WorkflowNodeError"
}
@dosubot[bot] commented on GitHub (Feb 7, 2026):
Hi @bright141! I'm Dosu and I’m helping the dify-official-plugins team.
This error is caused by stricter validation in Dify 1.12.1, which now requires a
file_markerfield inFileMessageobjects when a workflow tool is invoked from another workflow. The comfyui plugin doesn't explicitly set this field and relies on Dify core to handle file outputs, which leads to the validation error you’re seeing when chaining workflows. This is a known issue resulting from recent changes and instability in Dify’s file variable handling logic for tools and plugins, especially after a fix for custom tool file handling was merged and then reverted in the core platform [details].There isn’t an official workaround or patch for this specific error yet. The root cause is a mismatch between how the comfyui plugin emits file outputs (as blobs with metadata) and how Dify 1.12.1 expects file variables to be structured and validated when crossing workflow boundaries [core validation].
If you need an immediate solution, you may need to monitor for updates to either the comfyui plugin or Dify core that address this compatibility gap. If you’re comfortable with code, reviewing or patching the comfyui plugin to emit file messages with the required structure (including
file_marker) or adjusting Dify’s validation logic for cross-workflow tool outputs could resolve the issue. Otherwise, consider temporarily avoiding chaining workflows that rely on file outputs from the comfyui plugin until a fix is released.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other