Issues caused by retrying after installation failure #227

Closed
opened 2026-02-16 01:15:02 -05:00 by yindo · 2 comments
Owner

Originally created by @chuishi on GitHub (Jan 8, 2026).

Self Checks

To make sure we get to you in time, please check the following :)

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • "Please do not modify this template :) and fill in all the required fields."

Versions

  1. dify-plugin-daemon Version
  2. dify-api Version

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Originally created by @chuishi on GitHub (Jan 8, 2026). **Self Checks** To make sure we get to you in time, please check the following :) - [ ] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [ ] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [ ] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [ ] "Please do not modify this template :) and fill in all the required fields." **Versions** 1. dify-plugin-daemon Version 2. dify-api Version **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
yindo added the bug label 2026-02-16 01:15:02 -05:00
yindo closed this issue 2026-02-16 01:15:02 -05:00
Author
Owner

@chuishi commented on GitHub (Jan 8, 2026):

I encountered an error while installing a plugin. The installation was halfway completed, and it indicated success, but it actually didn't work. It kept reinstalling, consuming a lot of resources and causing other interfaces to timeout. Later, I deleted the data from the table and the physical installation files, and restarted the system, which resolved the issue. I would like to know if anyone else has encountered this problem or if it has been resolved in the new version.

@chuishi commented on GitHub (Jan 8, 2026): I encountered an error while installing a plugin. The installation was halfway completed, and it indicated success, but it actually didn't work. It kept reinstalling, consuming a lot of resources and causing other interfaces to timeout. Later, I deleted the data from the table and the physical installation files, and restarted the system, which resolved the issue. I would like to know if anyone else has encountered this problem or if it has been resolved in the new version.
Author
Owner

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

This issue has been addressed in recent versions. A unique index was added to the plugin installation table to prevent duplicate installation attempts, and the installation logic now includes safeguards to avoid repeated or concurrent installs that could consume resources and cause timeouts. These changes were merged on 2025-12-10, so upgrading to a version after that date should resolve the problem you described. If you still encounter similar issues, manual cleanup (removing database records and installation files, then restarting) remains a valid workaround, but it should be much less likely to be needed now.
You can see details of the fix here: fix: add unique index for plugin installation to prevent duplicate.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 8, 2026): <!-- Answer --> This issue has been addressed in recent versions. A unique index was added to the plugin installation table to prevent duplicate installation attempts, and the installation logic now includes safeguards to avoid repeated or concurrent installs that could consume resources and cause timeouts. These changes were merged on 2025-12-10, so upgrading to a version after that date should resolve the problem you described. If you still encounter similar issues, manual cleanup (removing database records and installation files, then restarting) remains a valid workaround, but it should be much less likely to be needed now. You can see details of the fix here: [fix: add unique index for plugin installation to prevent duplicate](https://github.com/langgenius/dify-plugin-daemon/pull/528). <!-- 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/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/2dbff9ea-ad83-4cac-af74-ae397bd25d79?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20issue%20has%20been%20addressed%20in%20recent%20versions.%20A%20unique%20index%20was%20added%20to%20the%20plugin%20installation%20table%20to%20prevent%20duplicate%20installation%20attempts%2C%20and%20the%20installation%20logic%20now%20includes%20safeguards%20to%20avoid%20repeated%20or%20concurrent%20installs%20that%20could%20consume%20resources%20and%20cause%20timeouts.%20These%20changes%20were%20merged%20on%202025-12-10%2C%20so%20upgrading%20to%20a%20version%20after%20that%20date%20should%20resolve%20the%20problem%20you%20described.%20If%20you%20still%20encounter%20similar%20issues%2C%20manual%20cleanup%20%28removing%20database%20records%20and%20installation%20files%2C%20then%20restarting%29%20remains%20a%20valid%20workaround%2C%20but%20it%20should%20be%20much%20less%20likely%20to%20be%20needed%20now.%20%20%0AYou%20can%20see%20details%20of%20the%20fix%20here%3A%20%5Bfix%3A%20add%20unique%20index%20for%20plugin%20installation%20to%20prevent%20duplicate%5D%28https%3A//github.com/langgenius/dify-plugin-daemon/pull/528%29.)&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-plugin-daemon/issues/560)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#227