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

Error: App unavailable, please check your app configurations. #15848

New Issue
Closed
opened 2026-02-21 19:23:39 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:23:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @JustGopher on GitHub (Aug 3, 2025).

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.7.1

Cloud or Self Hosted

Cloud

Steps to reproduce

I discovered this bug while using it on the official website. I noticed that this issue had appeared in issue #18664, and that issue had been closed. However, I encountered it again while using it on the official website.

I can access the application I've created normally when I open it from the studio, but when I try to access it from the workspace on the left side of the exploration page, this issue occurs.

Despite multiple attempts, the issue persists, while the studio page can be accessed normally in my application.

✔️ Expected Behavior

I should be able to enter normally from the left side of the exploration page

❌ Actual Behavior

Image Image Image
Originally created by @JustGopher on GitHub (Aug 3, 2025). ### 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 1.7.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce I discovered this bug while using it on the official website. **I noticed that this issue had appeared in issue #18664**, and that issue had been closed. However, I encountered it again while using it on the official website. I can access the application I've created normally when I open it from the studio, but when I try to access it from the workspace on the left side of the exploration page, this issue occurs. Despite multiple attempts, the issue persists, while the studio page can be accessed normally in my application. ### ✔️ Expected Behavior I should be able to enter normally from the left side of the exploration page ### ❌ Actual Behavior <img width="1367" height="954" alt="Image" src="https://github.com/user-attachments/assets/c727bd52-5d95-4fd1-8d72-6f8d1c5e2c70" /> <img width="1071" height="823" alt="Image" src="https://github.com/user-attachments/assets/f27fee5d-9aa2-4a9d-bd6d-7ede1b8e32f4" /> <img width="1052" height="954" alt="Image" src="https://github.com/user-attachments/assets/cdf0d960-6cb3-4a49-9b58-a182ac72d532" />
yindo closed this issue 2026-02-21 19:23:39 -05:00
yindo commented 2026-02-21 19:23:39 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 3, 2025):

Hi @JustGopher! I'm Dosu and I’m helping the dify team.

This error happens because the workspace/exploration page enforces stricter checks on app configuration, publication status, and user permissions than the studio. If the app is unpublished, missing required configuration (like workflow or model config), or you’re not in the correct workspace or lack permissions, you’ll see “App unavailable” even if the studio loads fine. This is a known pattern and has recurred for other users after recent updates to Dify’s authorization and error handling logic (example, recent PR).

To resolve: make sure the app is published, fully configured, and you’re in the correct workspace with the right permissions. If you’re accessing via a shared link, note that Dify (community version) does not auto-switch workspaces—you must manually switch first (reference). If everything looks correct and the error persists, it may be a regression from recent changes—other users have reported similar issues even after fixes (see here, here).

Republishing the app or double-checking the workspace context often resolves it. If not, this may need further investigation by the Dify cloud team.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Aug 3, 2025): <!-- Greeting --> Hi @JustGopher! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error happens because the workspace/exploration page enforces stricter checks on app configuration, publication status, and user permissions than the studio. If the app is unpublished, missing required configuration (like workflow or model config), or you’re not in the correct workspace or lack permissions, you’ll see “App unavailable” even if the studio loads fine. This is a known pattern and has recurred for other users after recent updates to Dify’s authorization and error handling logic ([example](https://github.com/langgenius/dify/issues/18664), [recent PR](https://github.com/langgenius/dify/pull/22524)). To resolve: make sure the app is published, fully configured, and you’re in the correct workspace with the right permissions. If you’re accessing via a shared link, note that Dify (community version) does not auto-switch workspaces—you must manually switch first ([reference](https://github.com/langgenius/dify/issues/21996)). If everything looks correct and the error persists, it may be a regression from recent changes—other users have reported similar issues even after fixes ([see here](https://github.com/langgenius/dify/issues/18395), [here](https://github.com/langgenius/dify/issues/18719)). Republishing the app or double-checking the workspace context often resolves it. If not, this may need further investigation by the Dify cloud team. <!-- 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/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/929c98b7-be97-41e8-af5f-2ae1925df07d?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/23335)
yindo commented 2026-02-21 19:23:39 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 3, 2025):

If the app is unpublished, missing required configuration (like workflow or model config), or you’re not in the correct workspace or lack permissions, you’ll see “App unavailable” even if the studio loads fine.

Have you published the application?

@crazywoola commented on GitHub (Aug 3, 2025): > If the app is unpublished, missing required configuration (like workflow or model config), or you’re not in the correct workspace or lack permissions, you’ll see “App unavailable” even if the studio loads fine. Have you published the application?
yindo commented 2026-02-21 19:23:39 -05:00
Author
Owner
Copy Link
Copy Source

@JustGopher commented on GitHub (Aug 4, 2025):

@crazywoola I understand. I haven't published my app yet. After publishing, I can enter it normally from the left side.

@JustGopher commented on GitHub (Aug 4, 2025): @crazywoola I understand. I haven't published my app yet. After publishing, I can enter it normally from the left side.
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
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#15848
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?