Start Node【Lark Triggers】, unable to select subscription,No subscribe button. #817

Closed
opened 2026-02-16 10:20:36 -05:00 by yindo · 4 comments
Owner

Originally created by @liuli404 on GitHub (Nov 20, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After I installed the Lark Triggers plugin, I added a subscription. Then, in the workflow, I added a 'Message Received' start node, but found that there was no button to add a subscription. It is inconsistent with the icons in the plugin help manual.

My Node Settings Page:
Image

Lark Triggers plugin version:
Image

✔️ Expected Behavior

In the help manual:
Image

Actual Behavior

No response

Originally created by @liuli404 on GitHub (Nov 20, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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 [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After I installed the Lark Triggers plugin, I added a subscription. Then, in the workflow, I added a 'Message Received' start node, but found that there was no button to add a subscription. It is inconsistent with the icons in the plugin help manual. My Node Settings Page: <img width="3200" height="1662" alt="Image" src="https://github.com/user-attachments/assets/5cee7b9a-153c-4c20-8acb-8d77c68b173b" /> Lark Triggers plugin version: <img width="832" height="906" alt="Image" src="https://github.com/user-attachments/assets/96ddb91f-a73e-43e0-8e1a-f4662bb0ef06" /> ### ✔️ Expected Behavior In the help manual: <img width="2986" height="1514" alt="Image" src="https://github.com/user-attachments/assets/b4b7fbce-7d75-4328-84a1-105e31ffa80f" /> ### ❌ Actual Behavior _No response_
yindo added the bug label 2026-02-16 10:20:36 -05:00
yindo closed this issue 2026-02-16 10:20:36 -05:00
Author
Owner

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

Hi @liuli404! I'm Dosu and I’m helping the dify team.

This issue is likely caused by a recent bug in the Lark Triggers plugin or its integration with the workflow UI. There was a recent fix merged for the Lark Triggers plugin that addressed problems with subscription configuration and event handling, including removing a check that could prevent proper operation if certain fields were missing. Updating the Lark Triggers plugin to the latest version (after November 17, 2025) should resolve issues where the subscription button or selection is missing in the workflow start node. You can review the relevant fix and update instructions here: fix: lark_trigger not work.

If you are still experiencing the issue after updating, double-check that your Docker environment exposes the necessary ports and that the plugin is running with the latest code. Also, ensure your workflow trigger node configuration is correct. Recent changes in the Dify UI may also affect how triggers and subscriptions are displayed, so updating both the core Dify platform and the plugin is recommended for best compatibility.

To reply, just mention @dosu.


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

@dosubot[bot] commented on GitHub (Nov 20, 2025): <!-- Greeting --> Hi @liuli404! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This issue is likely caused by a recent bug in the Lark Triggers plugin or its integration with the workflow UI. There was a recent fix merged for the Lark Triggers plugin that addressed problems with subscription configuration and event handling, including removing a check that could prevent proper operation if certain fields were missing. Updating the Lark Triggers plugin to the latest version (after November 17, 2025) should resolve issues where the subscription button or selection is missing in the workflow start node. You can review the relevant fix and update instructions here: [fix: lark_trigger not work](https://github.com/langgenius/dify-official-plugins/pull/2078). If you are still experiencing the issue after updating, double-check that your Docker environment exposes the necessary ports and that the plugin is running with the latest code. Also, ensure your workflow trigger node configuration is correct. Recent changes in the Dify UI may also affect how triggers and subscriptions are displayed, so updating both the core Dify platform and the plugin is recommended for best compatibility. <!-- 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/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/319962da-4d08-4432-a0e9-055032548cb7?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/issues/28459)
Author
Owner

@liuli404 commented on GitHub (Nov 20, 2025):

My plugin and Dify version are already up to date.

Lark Triggers plugin version:
Image

Dify version:
Image

Docker environment:

Image
@liuli404 commented on GitHub (Nov 20, 2025): My plugin and Dify version are already up to date. Lark Triggers plugin version: <img width="874" height="496" alt="Image" src="https://github.com/user-attachments/assets/7d1dc705-96c1-469c-9a75-a0064912a183" /> Dify version: <img width="1306" height="604" alt="Image" src="https://github.com/user-attachments/assets/9599cb88-cd80-4b39-bae3-8d2d847aa7d8" /> Docker environment: <img width="2934" height="368" alt="Image" src="https://github.com/user-attachments/assets/951f3e22-2f20-4387-a6cc-31eb3ec13321" />
Author
Owner

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

Based on your setup, the missing subscription button in the 'Message Received' node is likely because your subscription ("dc_feishu") is marked as "unused in workflows". The workflow UI only shows the subscription selector if there are subscriptions available and linked to the workflow trigger node. If the subscription isn't associated with any workflow, the UI won't display the selection button or controls for it.

To resolve this, try explicitly linking your subscription to the workflow trigger node. In the workflow editor, select the 'Message Received' node and look for an option to choose or assign a subscription. If no subscriptions appear, double-check that your plugin and Docker setup are running the latest code and that the backend API is correctly returning your subscription list. If the subscription is still marked as unused, you may need to re-create it or refresh the plugin panel so it's recognized as available for workflow triggers. This logic is confirmed by the workflow UI code and recent plugin updates (source, source).

If you continue to see this issue after confirming the above, check for any error logs in your Docker containers (web, API, plugin) that might indicate a backend or frontend failure in fetching or displaying subscriptions.

To reply, just mention @dosu.


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

@dosubot[bot] commented on GitHub (Nov 20, 2025): <!-- Answer --> Based on your setup, the missing subscription button in the 'Message Received' node is likely because your subscription ("dc_feishu") is marked as "unused in workflows". The workflow UI only shows the subscription selector if there are subscriptions available and linked to the workflow trigger node. If the subscription isn't associated with any workflow, the UI won't display the selection button or controls for it. To resolve this, try explicitly linking your subscription to the workflow trigger node. In the workflow editor, select the 'Message Received' node and look for an option to choose or assign a subscription. If no subscriptions appear, double-check that your plugin and Docker setup are running the latest code and that the backend API is correctly returning your subscription list. If the subscription is still marked as unused, you may need to re-create it or refresh the plugin panel so it's recognized as available for workflow triggers. This logic is confirmed by the workflow UI code and recent plugin updates ([source](https://github.com/langgenius/dify-official-plugins/issues/2080), [source](https://github.com/langgenius/dify/pull/28287)). If you continue to see this issue after confirming the above, check for any error logs in your Docker containers (web, API, plugin) that might indicate a backend or frontend failure in fetching or displaying subscriptions. <!-- 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/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0904cbef-92e1-48f6-beea-ca0ea8a02e0f?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&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/issues/28459)
Author
Owner

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

@liuli404 Let's pay attention to each other and follow up on the progress in the future. The question you raised, I also mentioned it:https://github.com/langgenius/dify-official-plugins/issues/2080

@andyqiuqiubo commented on GitHub (Nov 24, 2025): @liuli404 Let's pay attention to each other and follow up on the progress in the future. The question you raised, I also mentioned it:https://github.com/langgenius/dify-official-plugins/issues/2080
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#817