Plugins not launched concurrently — PLUGIN_LOCAL_LAUNCHING_CONCURRENT appears unused #145

Closed
opened 2026-02-16 00:20:07 -05:00 by yindo · 2 comments
Owner

Originally created by @homejim on GitHub (Jun 26, 2025).

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 0.1.0
  2. dify-api 1.4.1

Describe the bug
Hi, I noticed that the code includes a configuration called PLUGIN_LOCAL_LAUNCHING_CONCURRENT, but during application startup, the plugins are still being launched sequentially. It seems that this configuration is not actually being used or is not taking effect.

Is this feature not implemented yet, or is there another mechanism for controlling concurrent plugin startup? Thanks!

To Reproduce
Steps to reproduce the behavior:

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

Expected behavior
is there another way to configure concurrent plugin startup

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

Additional context
Add any other context about the problem here.

Originally created by @homejim on GitHub (Jun 26, 2025). **Self Checks** To make sure we get to you in time, please check the following :) - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify-plugin-daemon/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] "Please do not modify this template :) and fill in all the required fields." **Versions** 1. dify-plugin-daemon 0.1.0 2. dify-api 1.4.1 **Describe the bug** Hi, I noticed that the code includes a configuration called PLUGIN_LOCAL_LAUNCHING_CONCURRENT, but during application startup, the plugins are still being launched sequentially. It seems that this configuration is not actually being used or is not taking effect. Is this feature not implemented yet, or is there another mechanism for controlling concurrent plugin startup? Thanks! **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** is there another way to configure concurrent plugin startup **Screenshots** If applicable, add screenshots to help explain your problem. **Additional context** Add any other context about the problem here.
yindo closed this issue 2026-02-16 00:20:07 -05:00
Author
Owner

@homejim commented on GitHub (Jun 26, 2025):

@Yeuoly I have fixed this issue, and if needed, I will submit a pull request.

@homejim commented on GitHub (Jun 26, 2025): @Yeuoly I have fixed this issue, and if needed, I will submit a pull request.
Author
Owner

@homejim commented on GitHub (Jul 3, 2025):

@Yeuoly

@homejim commented on GitHub (Jul 3, 2025): @Yeuoly
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#145