dify - 💡(How to fix) Fix [Bug] Unable to remove non-existent apps from Explore page in self-hosted deployment

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. What issue are you experiencing?

In a self‑hosted Docker deployment, the Explore page continues to show apps that no longer exist in the workspace. These are “ghost” apps that were previously deleted or are otherwise inaccessible, but their entries remain in the Explore listing. There is no built‑in UI option to remove them.

2. Steps to reproduce

1. Deploy Dify (v1.14.1, Docker Compose on Windows WSL2, profile: postgresql + weaviate + collaboration).
2. Create several apps, some of which may be deleted via the API or the console.
3. Observe that deleted apps still appear on the Explore page (/explore/apps).
4. Attempting to open a ghost app shows an error (app not found / not available).
5. There is no “delete” or “hide” button for these ghost entries on Explore.

✔️ Expected Behavior

There should be a way (either via the console UI, API, or a documented CLI command) to permanently remove ghost/obsolete apps from the Explore page. Alternatively, the Explore page should automatically synchronise with the actual app list so that deleted apps do not persist.

❌ Actual Behavior

• The issue persists after multiple container restarts and after rebuilding the web image.
• This affects user experience because outdated apps clutter the Explore view and confuse users.
• A documented procedure or a built‑in admin tool to clean up Explore entries would be very helpful for self‑hosted administrators.

I am willing to help test a fix or provide additional logs if needed. However, I would first like to know the official recommended method to handle this situation.