langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

In the workflow, an error occurs when running the Lark trigger: subscription configuration is required. #808

New Issue
Closed
opened 2026-02-16 10:20:34 -05:00 by yindo · 6 comments
yindo commented 2026-02-16 10:20:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @andyqiuqiubo on GitHub (Nov 17, 2025).

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 Dify issues & Dify Official Plugins, 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

V1.10.0

Plugin version

V0.0.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Step 1: On the plugin page, the installation and configuration of Lark V0.0.2 were all successful.
Step 2: Create a new workflow and add a Lark trigger. At this point, a prompt appears: Not connected.
Step 3: Run the Lark trigger node. At this point, a prompt appears: Subscription configuration is required.

✔️ Error log

Image
Originally created by @andyqiuqiubo on GitHub (Nov 17, 2025). ### Self Checks - [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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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. ### Dify version V1.10.0 ### Plugin version V0.0.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Step 1: On the plugin page, the installation and configuration of Lark V0.0.2 were all successful. Step 2: Create a new workflow and add a Lark trigger. At this point, a prompt appears: Not connected. Step 3: Run the Lark trigger node. At this point, a prompt appears: Subscription configuration is required. ### ✔️ Error log <img width="2536" height="1229" alt="Image" src="https://github.com/user-attachments/assets/eb07f840-4dbe-404c-9781-2ab531b5bfb8" />
yindo added the bugstale labels 2026-02-16 10:20:34 -05:00
yindo closed this issue 2026-02-16 10:20:34 -05:00
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@andyqiuqiubo commented on GitHub (Nov 17, 2025):

@hjlarry , Please help check again, thank you. This issue occurred during the workflow operation after resolving the following problem: #2069

@andyqiuqiubo commented on GitHub (Nov 17, 2025): @hjlarry , Please help check again, thank you. This issue occurred during the workflow operation after resolving the following problem: #2069
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 17, 2025):

The "subscription configuration is required" error for the Lark trigger usually means the workflow node is missing required subscription properties—specifically, lark_encrypt_key or lark_verification_token. In recent updates, these checks were relaxed and the plugin was fixed to work even if these fields are not set, as long as the rest of the configuration is correct. The latest fix for this issue was merged today and should resolve the problem if you update to the newest version of the Lark trigger plugin and ensure your Docker setup exposes the necessary ports for plugin connectivity. You can review the details of the fix here.

If you are still seeing the error after updating, double-check your workflow's trigger node configuration and make sure your Docker environment exposes port 5001 and the plugin is running with the latest code. If the plugin is up to date and the environment is correct, the workflow trigger should connect and run without requiring manual subscription configuration.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 17, 2025): <!-- Answer --> The "subscription configuration is required" error for the Lark trigger usually means the workflow node is missing required subscription properties—specifically, `lark_encrypt_key` or `lark_verification_token`. In recent updates, these checks were relaxed and the plugin was fixed to work even if these fields are not set, as long as the rest of the configuration is correct. The latest fix for this issue was merged today and should resolve the problem if you update to the newest version of the Lark trigger plugin and ensure your Docker setup exposes the necessary ports for plugin connectivity. You can review the details of the fix [here](https://github.com/langgenius/dify-official-plugins/pull/2078). If you are still seeing the error after updating, double-check your workflow's trigger node configuration and make sure your Docker environment exposes port 5001 and the plugin is running with the latest code. If the plugin is up to date and the environment is correct, the workflow trigger should connect and run without requiring manual subscription configuration. <!-- 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/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6ba5cdbd-c7ea-49cd-a286-8f2ef6cdc601?feedback_type=other)</sup>&nbsp;&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-official-plugins/issues/2080)
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@hjlarry commented on GitHub (Nov 17, 2025):

@hjlarry , Please help check again, thank you. This issue occurred during the workflow operation after resolving the following problem: #2069

it should be resolved by this PR https://github.com/langgenius/dify/pull/28287

@hjlarry commented on GitHub (Nov 17, 2025): > [@hjlarry](https://github.com/hjlarry) , Please help check again, thank you. This issue occurred during the workflow operation after resolving the following problem: [#2069](https://github.com/langgenius/dify-official-plugins/issues/2069) it should be resolved by this PR https://github.com/langgenius/dify/pull/28287
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@andyqiuqiubo commented on GitHub (Nov 18, 2025):

@hjlarry, Okay, may I ask if this problem can only be solved after the next version of Dify Community Edition is released?

@andyqiuqiubo commented on GitHub (Nov 18, 2025): @hjlarry, Okay, may I ask if this problem can only be solved after the next version of Dify Community Edition is released?
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@bj-wangxiaoxiao commented on GitHub (Nov 27, 2025):

have you solved the problem?

@bj-wangxiaoxiao commented on GitHub (Nov 27, 2025): have you solved the problem?
yindo commented 2026-02-16 10:20:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 14, 2025):

Hi, @andyqiuqiubo. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported an error with the Lark plugin on Dify v1.10.0 where the trigger showed "Not connected" and required subscription configuration.
  • The problem was related to missing subscription properties like lark_encrypt_key or lark_verification_token.
  • Maintainer hjlarry identified the cause and implemented a fix in PR langgenius/dify#28287.
  • The fix relaxes the subscription requirements and will be included in a future Dify release.
  • You asked if the fix requires waiting for the next Dify Community Edition version, and another user inquired if the issue was resolved.

What's Next:

  • Please confirm if this issue is still relevant with the latest version of Dify once the fix is released by commenting here.
  • If I don’t hear back within 5 days, I will automatically close this issue.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 14, 2025): Hi, @andyqiuqiubo. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported an error with the Lark plugin on Dify v1.10.0 where the trigger showed "Not connected" and required subscription configuration. - The problem was related to missing subscription properties like lark_encrypt_key or lark_verification_token. - Maintainer hjlarry identified the cause and implemented a fix in PR langgenius/dify#28287. - The fix relaxes the subscription requirements and will be included in a future Dify release. - You asked if the fix requires waiting for the next Dify Community Edition version, and another user inquired if the issue was resolved. **What's Next:** - Please confirm if this issue is still relevant with the latest version of Dify once the fix is released by commenting here. - If I don’t hear back within 5 days, I will automatically close this issue. Thanks for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug stale
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-official-plugins#808
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?