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

bug(plugin): the frontend status will not be refreshed to "Installed" #21955

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

Originally created by @BeautyyuYanli on GitHub (Jan 28, 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

1.11.4

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

After installing the plugin, the frontend status will not be refreshed to "Installed", but I need to click the "Install" button second time to refresh the already installed plugin
Image

✔️ Expected Behavior

do it correctly

❌ Actual Behavior

No response

Originally created by @BeautyyuYanli on GitHub (Jan 28, 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 1.11.4 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce After installing the plugin, the frontend status will not be refreshed to "Installed", but I need to click the "Install" button second time to refresh the already installed plugin <img width="852" height="731" alt="Image" src="https://github.com/user-attachments/assets/82d56ee7-617b-415b-8469-28617adafaba" /> ### ✔️ Expected Behavior do it correctly ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:15:01 -05:00
yindo commented 2026-02-21 20:15:02 -05:00
Author
Owner
Copy Link
Copy Source

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

This is a known issue in Dify 1.11.4 (self-hosted) where the frontend plugin status doesn't automatically update to "Installed" after installation—you have to click "Install" again to refresh the state. The bug is tracked and has been reported in previous versions as well, sometimes requiring a second action or reinstall to update the UI correctly (example).

The frontend relies on hooks like useInstalledPluginList, useInstalledLatestVersion, and useInvalidateInstalledPluginList to fetch and refresh plugin data. The refresh is supposed to trigger after installation, but recent frontend refactors and possible issues in the status polling logic (such as in usePluginTaskStatus) may cause the UI not to update as expected after the first install action (source).

Common causes include the backend not reporting the install task state correctly, the frontend not polling or refreshing the plugin list after install, or asynchronous state not being handled properly in the UI. This is especially common in self-hosted Docker setups, where backend task state can become stale or incomplete (source).

Workarounds that have helped some users include: clearing browser cache or local storage, restarting the application or server, and (for advanced users) manually clearing related entries in the database (such as install_tasks, plugin_installations, plugin_declarations, ai_model_installations, and plugins tables in Postgres) if plugin tasks are stuck (example). If you are running in Docker, make sure your plugin manifests have the correct author field, set FORCE_VERIFYING_SIGNATURE=false in your Docker .env, and restart Docker services (example).

For maintainers, reviewing the refresh logic in the relevant frontend hooks and components (especially after recent refactors) and ensuring the backend always reports accurate install task state will help resolve this bug.

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 28, 2026): <!-- Answer --> This is a known issue in Dify 1.11.4 (self-hosted) where the frontend plugin status doesn't automatically update to "Installed" after installation—you have to click "Install" again to refresh the state. The bug is tracked and has been reported in previous versions as well, sometimes requiring a second action or reinstall to update the UI correctly [(example)](https://github.com/langgenius/dify/issues/12619#issuecomment-2582209756). The frontend relies on hooks like `useInstalledPluginList`, `useInstalledLatestVersion`, and `useInvalidateInstalledPluginList` to fetch and refresh plugin data. The refresh is supposed to trigger after installation, but recent frontend refactors and possible issues in the status polling logic (such as in `usePluginTaskStatus`) may cause the UI not to update as expected after the first install action [(source)](https://github.com/langgenius/dify/pull/30184). Common causes include the backend not reporting the install task state correctly, the frontend not polling or refreshing the plugin list after install, or asynchronous state not being handled properly in the UI. This is especially common in self-hosted Docker setups, where backend task state can become stale or incomplete [(source)](https://github.com/langgenius/dify/issues/21716). Workarounds that have helped some users include: clearing browser cache or local storage, restarting the application or server, and (for advanced users) manually clearing related entries in the database (such as `install_tasks`, `plugin_installations`, `plugin_declarations`, `ai_model_installations`, and `plugins` tables in Postgres) if plugin tasks are stuck [(example)](https://github.com/langgenius/dify/issues/16858#issuecomment-2754135925). If you are running in Docker, make sure your plugin manifests have the correct `author` field, set `FORCE_VERIFYING_SIGNATURE=false` in your Docker `.env`, and restart Docker services [(example)](https://github.com/langgenius/dify/issues/17397#issuecomment-2774770138). For maintainers, reviewing the refresh logic in the relevant frontend hooks and components (especially after recent refactors) and ensuring the backend always reports accurate install task state will help resolve this bug. <!-- 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/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/cc7c4a56-bb34-4053-88f0-47095e8b113f?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%20in%20Dify%201.11.4%20%28self-hosted%29%20where%20the%20frontend%20plugin%20status%20doesn%27t%20automatically%20update%20to%20%22Installed%22%20after%20installation%E2%80%94you%20have%20to%20click%20%22Install%22%20again%20to%20refresh%20the%20state.%20The%20bug%20is%20tracked%20and%20has%20been%20reported%20in%20previous%20versions%20as%20well%2C%20sometimes%20requiring%20a%20second%20action%20or%20reinstall%20to%20update%20the%20UI%20correctly%20%5B%28example%29%5D%28https%3A//github.com/langgenius/dify/issues/12619%23issuecomment-2582209756%29.%0A%0AThe%20frontend%20relies%20on%20hooks%20like%20%60useInstalledPluginList%60%2C%20%60useInstalledLatestVersion%60%2C%20and%20%60useInvalidateInstalledPluginList%60%20to%20fetch%20and%20refresh%20plugin%20data.%20The%20refresh%20is%20supposed%20to%20trigger%20after%20installation%2C%20but%20recent%20frontend%20refactors%20and%20possible%20issues%20in%20the%20status%20polling%20logic%20%28such%20as%20in%20%60usePluginTaskStatus%60%29%20may%20cause%20the%20UI%20not%20to%20update%20as%20expected%20after%20the%20first%20install%20action%20%5B%28source%29%5D%28https%3A//github.com/langgenius/dify/pull/30184%29.%0A%0ACommon%20causes%20include%20the%20backend%20not%20reporting%20the%20install%20task%20state%20correctly%2C%20the%20frontend%20not%20polling%20or%20refreshing%20the%20plugin%20list%20after%20install%2C%20or%20asynchronous%20state%20not%20being%20handled%20properly%20in%20the%20UI.%20This%20is%20especially%20common%20in%20self-hosted%20Docker%20setups%2C%20where%20backend%20task%20state%20can%20become%20stale%20or%20incomplete%20%5B%28source%29%5D%28https%3A//github.com/langgenius/dify/issues/21716%29.%0A%0AWorkarounds%20that%20have%20helped%20some%20users%20include%3A%20clearing%20browser%20cache%20or%20local%20storage%2C%20restarting%20the%20application%20or%20server%2C%20and%20%28for%20advanced%20users%29%20manually%20clearing%20related%20entries%20in%20the%20database%20%28such%20as%20%60install_tasks%60%2C%20%60plugin_installations%60%2C%20%60plugin_declarations%60%2C%20%60ai_model_installations%60%2C%20and%20%60plugins%60%20tables%20in%20Postgres%29%20if%20plugin%20tasks%20are%20stuck%20%5B%28example%29%5D%28https%3A//github.com/langgenius/dify/issues/16858%23issuecomment-2754135925%29.%20If%20you%20are%20running%20in%20Docker%2C%20make%20sure%20your%20plugin%20manifests%20have%20the%20correct%20%60author%60%20field%2C%20set%20%60FORCE_VERIFYING_SIGNATURE%3Dfalse%60%20in%20your%20Docker%20%60.env%60%2C%20and%20restart%20Docker%20services%20%5B%28example%29%5D%28https%3A//github.com/langgenius/dify/issues/17397%23issuecomment-2774770138%29.%0A%0AFor%20maintainers%2C%20reviewing%20the%20refresh%20logic%20in%20the%20relevant%20frontend%20hooks%20and%20components%20%28especially%20after%20recent%20refactors%29%20and%20ensuring%20the%20backend%20always%20reports%20accurate%20install%20task%20state%20will%20help%20resolve%20this%20bug.)&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/31668)
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 🐞 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#21955
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?