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

[Dify Cloud] Draft workflows disappeared after recent update (not published) #21826

New Issue
Open
opened 2026-02-21 20:14:30 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:14:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @weiyanyan118-coder on GitHub (Jan 21, 2026).

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

Dify 1.11.4

Cloud or Self Hosted

Cloud

Steps to reproduce

Description

I am using Dify Cloud (cloud.dify.ai) with the same account and workspace.

All workflows created in the last two weeks were in draft status (never published).
After a recent cloud update, these draft workflows are no longer visible in the UI.

Older published workflows still exist normally.

✔️ Expected Behavior

Draft workflows should remain visible or be recoverable.

❌ Actual Behavior

All draft workflows created recently are missing from the workflow list.

Additional context

  • Cloud version
  • Same account & same workspace
  • Multiple workflows affected
  • Workflows include Excel → ForEach → LLM → Feishu nodes

This seems to be a draft workflow visibility or version pointer issue rather than user deletion.
Please help check whether the draft workflow records (graph_json) still exist and can be restored.

Originally created by @weiyanyan118-coder on GitHub (Jan 21, 2026). ### 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 Dify 1.11.4 ### Cloud or Self Hosted Cloud ### Steps to reproduce ### Description I am using Dify Cloud (cloud.dify.ai) with the same account and workspace. All workflows created in the last two weeks were in **draft status (never published)**. After a recent cloud update, these draft workflows are no longer visible in the UI. Older published workflows still exist normally. ### ✔️ Expected Behavior Draft workflows should remain visible or be recoverable. ### ❌ Actual Behavior All draft workflows created recently are missing from the workflow list. ### Additional context - Cloud version - Same account & same workspace - Multiple workflows affected - Workflows include Excel → ForEach → LLM → Feishu nodes This seems to be a draft workflow visibility or version pointer issue rather than user deletion. Please help check whether the draft workflow records (graph_json) still exist and can be restored.
yindo added the 🐞 bugcloud labels 2026-02-21 20:14:30 -05:00
yindo commented 2026-02-21 20:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 21, 2026):

Hi @weiyanyan118-coder! I'm Dosu and I’m helping the dify team.

This is a known issue that can happen after Dify Cloud updates—draft workflows may disappear from the UI due to backend filtering or schema changes, not deletion. The draft workflow data is stored in the backend with a version='draft' flag and the workflow structure in the graph field. If the draft record still exists, it should be recoverable and visible; if not, it's usually due to a migration or pointer issue, not user action or deletion.

In similar cases, users have found that missing workflows could sometimes be found by searching or direct URL, indicating a UI filtering problem rather than true loss. However, in Dify Cloud, you can't run migrations or check the database directly yourself. The best next step is to provide Dify Cloud support with details like affected app IDs, workflow names, and creation dates, and ask them to check for the presence of draft workflow records in the backend and restore visibility if possible. This issue has also affected other entities (like Knowledge Bases) after cloud updates, where data remained in the backend but was hidden in the UI due to permission or filtering changes [example].

If you have a direct link or remember the workflow name, try searching for it or accessing it by URL to rule out a UI-only filtering issue [example]. Otherwise, backend support will need to confirm if the draft records (with the graph field) still exist and can be restored [example].

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 (Jan 21, 2026): <!-- Greeting --> Hi @weiyanyan118-coder! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known issue that can happen after Dify Cloud updates—draft workflows may disappear from the UI due to backend filtering or schema changes, not deletion. The draft workflow data is stored in the backend with a `version='draft'` flag and the workflow structure in the `graph` field. If the draft record still exists, it should be recoverable and visible; if not, it's usually due to a migration or pointer issue, not user action or deletion. In similar cases, users have found that missing workflows could sometimes be found by searching or direct URL, indicating a UI filtering problem rather than true loss. However, in Dify Cloud, you can't run migrations or check the database directly yourself. The best next step is to provide Dify Cloud support with details like affected app IDs, workflow names, and creation dates, and ask them to check for the presence of draft workflow records in the backend and restore visibility if possible. This issue has also affected other entities (like Knowledge Bases) after cloud updates, where data remained in the backend but was hidden in the UI due to permission or filtering changes [[example](https://github.com/langgenius/dify/issues/26458)]. If you have a direct link or remember the workflow name, try searching for it or accessing it by URL to rule out a UI-only filtering issue [[example](https://github.com/langgenius/dify/issues/21532)]. Otherwise, backend support will need to confirm if the draft records (with the `graph` field) still exist and can be restored [[example](https://github.com/langgenius/dify/issues/22008#issuecomment-3047374182)]. <!-- 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/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/d3aad900-2de8-490f-bff0-d23ab08fd73b?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=This%20is%20a%20known%20issue%20that%20can%20happen%20after%20Dify%20Cloud%20updates%E2%80%94draft%20workflows%20may%20disappear%20from%20the%20UI%20due%20to%20backend%20filtering%20or%20schema%20changes%2C%20not%20deletion.%20The%20draft%20workflow%20data%20is%20stored%20in%20the%20backend%20with%20a%20%60version%3D%27draft%27%60%20flag%20and%20the%20workflow%20structure%20in%20the%20%60graph%60%20field.%20If%20the%20draft%20record%20still%20exists%2C%20it%20should%20be%20recoverable%20and%20visible%3B%20if%20not%2C%20it%27s%20usually%20due%20to%20a%20migration%20or%20pointer%20issue%2C%20not%20user%20action%20or%20deletion.%20%0A%0AIn%20similar%20cases%2C%20users%20have%20found%20that%20missing%20workflows%20could%20sometimes%20be%20found%20by%20searching%20or%20direct%20URL%2C%20indicating%20a%20UI%20filtering%20problem%20rather%20than%20true%20loss.%20However%2C%20in%20Dify%20Cloud%2C%20you%20can%27t%20run%20migrations%20or%20check%20the%20database%20directly%20yourself.%20The%20best%20next%20step%20is%20to%20provide%20Dify%20Cloud%20support%20with%20details%20like%20affected%20app%20IDs%2C%20workflow%20names%2C%20and%20creation%20dates%2C%20and%20ask%20them%20to%20check%20for%20the%20presence%20of%20draft%20workflow%20records%20in%20the%20backend%20and%20restore%20visibility%20if%20possible.%20This%20issue%20has%20also%20affected%20other%20entities%20%28like%20Knowledge%20Bases%29%20after%20cloud%20updates%2C%20where%20data%20remained%20in%20the%20backend%20but%20was%20hidden%20in%20the%20UI%20due%20to%20permission%20or%20filtering%20changes%20%5B%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/26458%29%5D.%0A%0AIf%20you%20have%20a%20direct%20link%20or%20remember%20the%20workflow%20name%2C%20try%20searching%20for%20it%20or%20accessing%20it%20by%20URL%20to%20rule%20out%20a%20UI-only%20filtering%20issue%20%5B%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/21532%29%5D.%20Otherwise%2C%20backend%20support%20will%20need%20to%20confirm%20if%20the%20draft%20records%20%28with%20the%20%60graph%60%20field%29%20still%20exist%20and%20can%20be%20restored%20%5B%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/22008%23issuecomment-3047374182%29%5D.)&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/31373)
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 cloud 🐞 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#21826
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?