Skip to content

There are several different versions of plugins running in the background #18845

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 tasks done
AAlexDing opened this issue Apr 27, 2025 · 2 comments
Open
5 tasks done
Assignees
Labels
🐞 bug Something isn't working

Comments

@AAlexDing
Copy link
Contributor

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Install several versions of the plugin then use top to check the process info.

✔️ Expected Behavior

Ignore previous versions, only run the latest version.

❌ Actual Behavior

Image

@dosubot dosubot bot added the 🐞 bug Something isn't working label Apr 27, 2025
Copy link

dosubot bot commented Apr 27, 2025

To ensure only the latest version of a plugin is running in Dify, you can update plugins by clicking the "Plugins" button on the Dify platform homepage, selecting the plugin that needs updating, and clicking the "Upgrade" button next to the plugin title. This process ensures that workflows automatically use the latest version of plugins installed in the workspace, and only one version of a plugin can exist in a workspace at any time [1][2].

If you are experiencing issues with multiple versions running, it might be due to caching. You can resolve this by downloading the plugin installation package locally, manually modifying the version number in the package, and then uploading and installing the modified local plugin. This forces the system to recognize it as a new plugin, bypassing any caching mechanisms that might prevent the new features from appearing [3].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@junjiem
Copy link
Contributor

junjiem commented Apr 27, 2025

Did you forcibly enable the cloud mode? If so, it's not surprising. Plugins are isolated in each workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants