Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix [Dify Cloud] All LLM nodes report "model not exists" after browser cache cleared [2 comments, 3 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#35565•Fetched 2026-04-26 05:24:38
View on GitHub
Comments
2
Participants
3
Timeline
6
Reactions
3
Author
GinkoooooooGinkooooooo
Participants
812yim812yimGinkoooooooGinkoooooooherricaneherricane
Timeline (top)
commented ×2labeled ×2mentioned ×1subscribed ×1

Error Message

All LLM nodes in any workflow (including newly created blank workflows) report the error model not exists, regardless of which model provider (OpenAI, Anthropic, etc.) or which specific model is selected. 5. Run the node — the error model not exists appears.

  • Testing in incognito mode yields the same error.
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

Dify Cloud

Cloud or Self Hosted

Cloud

Steps to reproduce

Self Checks

  • This is a bug for Dify Cloud (cloud.dify.ai), not a self-hosted instance.
  • I have searched the existing issues and confirmed this is a new bug.

Describe the bug All LLM nodes in any workflow (including newly created blank workflows) report the error model not exists, regardless of which model provider (OpenAI, Anthropic, etc.) or which specific model is selected.

To Reproduce

  1. Log into Dify Cloud (account: [email protected]).
  2. Go to Settings → Model Providers, ensure at least one provider (e.g., OpenAI) has a valid API key configured and models added.
  3. Create a new blank Chatflow or Workflow.
  4. Add an LLM node, select any model from the dropdown.
  5. Run the node — the error model not exists appears.

Expected behavior The LLM node should successfully invoke the selected model and return a response.

Environment

  • Dify Cloud (cloud.dify.ai)
  • Account: [email protected]
  • Issue started: approx. 2026/04/25

Additional context

  • API keys have been verified as valid.
  • All browser site data (LocalStorage, SessionStorage, IndexedDB, Cookies) has been cleared.
  • Testing in incognito mode yields the same error.
  • Deleting and re-adding models has no effect.
  • The issue occurs in all workflows, including new blank ones.
  • Suspect a platform-side model loading or plugin daemon failure.

✔️ Expected Behavior

The LLM node should successfully invoke the selected model and return a response.

❌ Actual Behavior

"model xxx not exists"

<img width="808" height="1476" alt="Image" src="https://github.com/user-attachments/assets/211508c4-3061-4074-a4da-09933f9244db" />

extent analysis

TL;DR

The issue can be resolved by investigating and fixing the model loading or plugin daemon failure on the Dify Cloud platform.

Guidance

  • Verify the model configuration and API keys for each provider to ensure they are correct and valid.
  • Check the platform's plugin daemon logs for any errors or issues related to model loading.
  • Test the LLM node with different models and providers to isolate the issue.
  • Consider reaching out to the Dify Cloud support team for further assistance, as the issue seems to be platform-side.

Example

No code snippet is provided as the issue seems to be related to the Dify Cloud platform configuration rather than a code-specific problem.

Notes

The issue may be related to a platform-side configuration or plugin daemon failure, and resolving it may require assistance from the Dify Cloud support team.

Recommendation

Apply workaround: Reach out to the Dify Cloud support team for further assistance, as the issue seems to be platform-side and may require their intervention to resolve.

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#model loading#API versioning#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING