mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-21 17:45:23 -04:00
The Lark Trigger plugin is not configurable. #802
Reference in New Issue
Block a user
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?
Originally created by @andyqiuqiubo on GitHub (Nov 16, 2025).
Self Checks
Dify version
V1.10.0
Plugin version
0.0.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
After successfully installing the Lark Trigger plugin, when configuring the Lark Trigger plugin again, the error shown in the screenshot is encountered.
✔️ Error log
@dosubot[bot] commented on GitHub (Nov 16, 2025):
The error
'langgenius/lark_trigger/lark_trigger not found'is likely caused by a recent folder rename in the plugin codebase. The Lark Trigger plugin folder was changed fromtriggers/larktotriggers/lark_triggerto match naming conventions for other trigger plugins. If your deployment or configuration references the old folder name, Dify won't be able to find the trigger provider, resulting in the error you see when trying to reconfigure the plugin.To resolve this, make sure your plugin installation and Docker volumes are up to date and that Dify is referencing the correct, current folder name (
lark_trigger). You may need to restart your plugin daemon and API containers after updating the plugin files to ensure the new folder structure is recognized. This change was merged very recently, so if you installed or updated the plugin before the rename, a fresh install or update should fix the issue.See details in the merged PR.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@andyqiuqiubo commented on GitHub (Nov 16, 2025):
@dosu, I installed the plugin only after changing the folder of the Feishu trigger plugin from triggers/lark to triggers/lark_trigger, so there is no deployment or configuration that references the old folder name.
@dosubot[bot] commented on GitHub (Nov 16, 2025):
Thanks for clarifying your install process. Since you installed after the folder was renamed and there are no legacy references, the error is likely caused by something else—most commonly, a mismatch or stale cache in plugin registration, or a Docker/network config issue.
Here are the most likely causes and steps to check:
triggers/lark_triggermatch what Dify expects. Any mismatch between the manifest's provider path and the actual folder name will cause discovery failures, especially after a rename.ports: - "5001:5001"if your plugin daemon uses that port). Missing or incorrect port mappings can prevent Dify from reaching the plugin, resulting in "not found" errors—even if the folder name is correct. This has resolved similar issues for other plugins in self-hosted Docker setups (example).If you confirm the above and still see the error, let me know what you find in the logs or if you spot any mismatches in the manifest or Docker config.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@hjlarry commented on GitHub (Nov 16, 2025):
There are a few additional issues with this plugin, and we will address them soon.
@andyqiuqiubo commented on GitHub (Nov 17, 2025):
@hjlarry , Thank you for your prompt reply
@andyqiuqiubo commented on GitHub (Nov 17, 2025):
After using lark version 0.0.2, the plugin page can be configured normally. Close this issue.