Issue Station
Sign In
Tools hereToolbox

dify - ✅(Solved) Fix After deploying Dify version 1.14.0, the error "This form has already been submitted by another user ..." appears when using the HITL node. [1 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35703•Fetched 2026-04-30 06:45:24
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
1
Author
xiaolvzi25xiaolvzi25
Participants
QuantumGhostQuantumGhostxiaolvzi25xiaolvzi25
Timeline (top)
labeled ×2commented ×1cross-referenced ×1

PR fix notes

PR #113: fix: fix file deserialzation error

Description (problem / solution / changelog)

This PR restores compatibility when deserializing historical File payloads produced before 749751d.

Changes:

  • Updated graphon.file.models.File to accept historical normalized fields (id / type) during deserialization while preserving the current constructor surface.
  • Introduced a private internal error for conflicting constructor inputs instead of raising a generic ValueError.
  • Added regression coverage using JSON fixtures generated from 749751d^:
    • direct File deserialization from historical JSON
    • GraphRuntimeState.from_snapshot(...) deserialization from a historical snapshot containing a file variable

Validation:

  • Targeted file/runtime tests pass
  • Full test suite passes (324 passed)

Related Issue

Closes #langgenius/dify#35703

Summary

Checklist

  • This pull request links the issue it resolves or advances
  • This pull request title follows Conventional Commits, and any breaking change is marked with !
  • If CLA Assistant prompted me, I signed CLA.md in the pull request conversation

Changed files

  • src/graphon/file/models.py (modified, +28/-3)
  • tests/file/test_models.py (modified, +36/-0)
  • tests/runtime/test_graph_runtime_state.py (modified, +77/-0)
RAW_BUFFERClick to expand / collapse

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

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

<img width="1629" height="898" alt="Image" src="https://github.com/user-attachments/assets/1d601916-a279-4c48-a888-e50f6fec94dc" />

✔️ Expected Behavior

Now that the HITL node is arranged in the workflow, the process cannot proceed further. This appears to be a bug; we hope the issue can be investigated, confirmed, and resolved.

❌ Actual Behavior

No response

extent analysis

TL;DR

The issue may be related to the HITL node configuration or workflow setup in the self-hosted Dify Docker environment.

Guidance

  • Review the workflow configuration to ensure the HITL node is properly connected and configured.
  • Check the Docker container logs for any error messages related to the HITL node or workflow processing.
  • Verify that the HITL node is correctly arranged in the workflow and that there are no other nodes or dependencies blocking the process.
  • Consider providing more details about the workflow setup and HITL node configuration for further assistance.

Notes

The issue lacks specific technical details, making it challenging to provide a precise solution. Additional information about the workflow, HITL node configuration, and any error messages would be helpful in troubleshooting the issue.

Recommendation

Apply workaround: Provide more details about the workflow setup and HITL node configuration to help investigate the issue further.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#configuration error#environment variable#network issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - ✅(Solved) Fix After deploying Dify version 1.14.0, the error "This form has already been submitted by another user ..." appears when using the HITL node. [1 pull requests, 1 comments, 2 participants]