dify - 💡(How to fix) Fix When creating new app, app is not fully initialized. [5 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#35167Fetched 2026-04-15 06:45:39
View on GitHub
Comments
5
Participants
2
Timeline
7
Reactions
1
Author
Participants
Timeline (top)
commented ×5cross-referenced ×1labeled ×1
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

1.13.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Create a new app from blank.

✔️ Expected Behavior

Apps editor in Studio opens, editing the app is possible.

❌ Actual Behavior

App page opens in studio, processing indiciator active indefintely. Editing app is not possible. However, if you choose to import from DSL and import, eg a blank app with only "INPUT" you can start working with it normally.

extent analysis

TL;DR

The issue can be potentially resolved by investigating the differences between creating a new app from blank and importing a blank app from DSL, to identify the root cause of the indefinite processing indicator.

Guidance

  • Verify that the issue persists when creating a new app from blank in a minimal environment, without any additional configurations or dependencies.
  • Compare the internal state of the app when created from blank versus imported from DSL, to identify any discrepancies that might be causing the processing indicator to remain active.
  • Check if there are any specific error messages or warnings in the console or logs when creating a new app from blank, which could provide clues about the root cause.
  • Attempt to import a minimal app from DSL, with only the necessary components, to see if the issue is related to the complexity of the app or a specific feature.

Notes

The issue seems to be specific to creating a new app from blank, and the fact that importing a blank app from DSL works normally suggests that there might be a difference in how the app is initialized or configured in these two scenarios.

Recommendation

Apply workaround: Import a minimal blank app from DSL to start working on the app, while investigating the root cause of the issue with creating a new app from blank. This allows users to continue working on their apps while the issue is being resolved.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING