Variables disappear, can not product new variable at all v0.11.4

[tnfsmith]

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

v.1.11.4

Cloud or Self Hosted

Self Hosted (Source), Self Hosted (Docker)

Steps to reproduce

Hi, since update from v1.11.3 and now .4. The variables can no re-product. It always get error, can not save workflow at all.

✔️ Expected Behavior

work like v1.11.2

❌ Actual Behavior

No response

[dosubot]

This is a known regression in v1.11.4: after upgrading from v1.11.3, variables may disappear or can't be created, which blocks workflow saving. The root cause is a breaking change that now requires every workflow node output to include a value_type field. Workflows created before this change may lack this field, causing validation errors and preventing saves. The backend also now enforces stricter validation on variable operations, so any mismatch between frontend data and backend expectations (like missing value_type) can trigger these issues.

There’s no official migration script yet. As a workaround, try re-importing the end node and setting variables again. If that doesn’t help and you need an urgent fix, downgrading to your previous stable version is recommended until a patch is released. Maintainers are aware and working on a fix. More details and discussion are available here.

To reply, just mention @dosu.

---

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

   

[tnfsmith]

.

Checklist always invalid, what the heck the, I don't know

[dosubot]

This "Invalid variable" checklist error is a known pain point after the v1.11.4 update. Dify now requires every variable (including those used in HTTP Request nodes) to have a type ("value_type") and be defined somewhere earlier in the workflow. If a variable is missing, misspelled, or lacks this metadata, the checklist will block you from saving or running the workflow—but it only shows a generic error, not which variable is the problem, which makes debugging frustrating (source).

Here’s what you can try:

• Double-check all variable references in your HTTP Request node for typos or missing variables.
• Make sure every variable you use is actually created by a previous node and has a type assigned.
• If you’re referencing variables in a JSON body, try putting them in double quotes (e.g., "{{your_var}}")—this has fixed similar issues for others (source).
• If you recently upgraded, try deleting and re-adding the affected node(s), or recreating the variables from scratch.
• Recent fixes (PRs fix: allow None values in VariableMessage validation #30082, fix: fix object value is optional should skip validate #30894) have improved validation for optional/null values and JSON objects, so updating to the latest patch may help if you’re not already on it.

If you’re comfortable editing workflow JSON, you can export your workflow, look for missing "value_type" fields in variable definitions, and add them manually as a workaround.

If you want more targeted help, feel free to share the specific variable reference or a snippet of your workflow config. The maintainers are aware of this issue and are working on making the error messages more helpful in future releases.

To reply, just mention @dosu.

---

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

   

[tnfsmith]

No, no, I try to create new workflow and then do the same with my existed workflow like before. Create brand new and the error still sit there. Sadly, it error may related to the cores

[dosubot]

This error is caused by a regression in Dify v1.11.4’s core backend logic for variable handling. Recent changes introduced stricter validation and a new centralized variable persistence layer, which now affects both new and existing workflows. The “Invalid variable” checklist error usually means a variable is missing, misreferenced, or lacks required metadata (like value_type), and the backend now enforces this much more strictly—even for brand new workflows. This isn’t related to CPU or worker “cores,” but rather to the core workflow engine and variable validation logic itself source.

To troubleshoot: check that every variable you reference is created by a previous node and has a type assigned. If you’re comfortable, export your workflow JSON and look for missing value_type fields in variable definitions. Sometimes, deleting and re-adding nodes or variables can help, but in this version, even new workflows can hit this bug. If you need to get unblocked urgently, downgrading to your previous stable version is the only reliable workaround until a patch is released.

If you can share backend error logs or a snippet of your workflow config, I can help pinpoint exactly which variable or field is causing the failure. The maintainers are aware and working on a fix.

To reply, just mention @dosu.

---

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