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

Output Variables disappear after a few minutes in langgenius/lark_trigger plugin #963

New Issue
Closed
opened 2026-02-16 10:21:08 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 10:21:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @Linyilan-zz on GitHub (Feb 2, 2026).

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

Version1.11.4

Plugin version

0.0.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Deploy the langgenius/lark_trigger plugin in Dify.

Configure the plugin and verify that the "Message Received" → "Output Variables" are correctly populated.

Wait for around 10–15 minutes after deployment.

Observe that the Output Variables fields are now empty.

other plugins are unable to select or use these variables.

Expected behavior:
Output Variables should remain available and consistent after deployment, so that downstream plugins can access them.

Actual behavior:
Output Variables are initially populated correctly, but after ~10–15 minutes they become empty, breaking dependent workflows.

Additional information:

Plugin: langgenius/lark_trigger

Node: "Message Received"

Environment: Dify Workflow

Image Image

✔️ Error log

No response

Originally created by @Linyilan-zz on GitHub (Feb 2, 2026). ### 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 Version1.11.4 ### Plugin version 0.0.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Deploy the langgenius/lark_trigger plugin in Dify. Configure the plugin and verify that the "Message Received" → "Output Variables" are correctly populated. Wait for around 10–15 minutes after deployment. Observe that the Output Variables fields are now empty. other plugins are unable to select or use these variables. Expected behavior: Output Variables should remain available and consistent after deployment, so that downstream plugins can access them. Actual behavior: Output Variables are initially populated correctly, but after ~10–15 minutes they become empty, breaking dependent workflows. Additional information: Plugin: langgenius/lark_trigger Node: "Message Received" Environment: Dify Workflow <img width="754" height="1224" alt="Image" src="https://github.com/user-attachments/assets/49d78195-cd07-4ff2-b1b2-9243a199801a" /> <img width="698" height="568" alt="Image" src="https://github.com/user-attachments/assets/d7fcab72-8296-460d-b773-7ba9d9d39020" /> ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:21:08 -05:00
yindo closed this issue 2026-02-16 10:21:08 -05:00
yindo commented 2026-02-16 10:21:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 2, 2026):

Hi @Linyilan-zz! I'm Dosu and I’m helping the dify-official-plugins team.

This is a known issue in Dify v1.11.4 and is not caused by the langgenius/lark_trigger plugin itself. Output Variables for trigger nodes like "Message Received" are dynamically built from the plugin's output schema in the frontend, but this schema isn't persisted with the workflow node. As a result, variables disappear after some time, navigation, or reload, breaking downstream workflows. The backend only saves execution outputs for tracing, not for restoring the design-time schema, which is why the problem occurs. This affects all trigger plugins, not just Lark Trigger, and is tracked in several Dify issues (#31146, #31352, #31542).

There is no official workaround yet. Some users have had partial success by re-importing nodes or resetting variables, but these are not guaranteed fixes. If you enable "Subscription" on the LARK_TRIGGER and the event does not supply an output schema, the output variables panel will disappear and downstream nodes cannot reference trigger outputs, causing validation errors (source). Keeping your plugin and Docker setup up to date and ensuring the subscription is correctly linked may help in some cases, but the limitation will persist until Dify adds persistent schema support for trigger outputs.

If you want to help maintainers prioritize a fix, sharing workflow exports, error logs, or detailed reproduction steps in the main Dify issues can be useful. You can track progress in issue #1542 and related threads.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 2, 2026): <!-- Greeting --> Hi @Linyilan-zz! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify-official-plugins team. <!-- Answer --> This is a known issue in Dify v1.11.4 and is not caused by the langgenius/lark_trigger plugin itself. Output Variables for trigger nodes like "Message Received" are dynamically built from the plugin's output schema in the frontend, but this schema isn't persisted with the workflow node. As a result, variables disappear after some time, navigation, or reload, breaking downstream workflows. The backend only saves execution outputs for tracing, not for restoring the design-time schema, which is why the problem occurs. This affects all trigger plugins, not just Lark Trigger, and is tracked in several Dify issues ([#31146](https://github.com/langgenius/dify/issues/31146), [#31352](https://github.com/langgenius/dify/issues/31352), [#31542](https://github.com/langgenius/dify/issues/31542)). There is no official workaround yet. Some users have had partial success by re-importing nodes or resetting variables, but these are not guaranteed fixes. If you enable "Subscription" on the LARK_TRIGGER and the event does not supply an output schema, the output variables panel will disappear and downstream nodes cannot reference trigger outputs, causing validation errors ([source](https://github.com/langgenius/dify/issues/31210)). Keeping your plugin and Docker setup up to date and ensuring the subscription is correctly linked may help in some cases, but the limitation will persist until Dify adds persistent schema support for trigger outputs. If you want to help maintainers prioritize a fix, sharing workflow exports, error logs, or detailed reproduction steps in the main Dify issues can be useful. You can track progress in [issue #1542](https://github.com/langgenius/dify/issues/1542) and related threads. <!-- 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/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/80b89c29-1f39-4194-8ea0-dccd731dcefa?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Dify%20v1.11.4%20and%20is%20not%20caused%20by%20the%20langgenius/lark_trigger%20plugin%20itself.%20Output%20Variables%20for%20trigger%20nodes%20like%20%22Message%20Received%22%20are%20dynamically%20built%20from%20the%20plugin%27s%20output%20schema%20in%20the%20frontend%2C%20but%20this%20schema%20isn%27t%20persisted%20with%20the%20workflow%20node.%20As%20a%20result%2C%20variables%20disappear%20after%20some%20time%2C%20navigation%2C%20or%20reload%2C%20breaking%20downstream%20workflows.%20The%20backend%20only%20saves%20execution%20outputs%20for%20tracing%2C%20not%20for%20restoring%20the%20design-time%20schema%2C%20which%20is%20why%20the%20problem%20occurs.%20This%20affects%20all%20trigger%20plugins%2C%20not%20just%20Lark%20Trigger%2C%20and%20is%20tracked%20in%20several%20Dify%20issues%20%28%5B%2331146%5D%28https%3A//github.com/langgenius/dify/issues/31146%29%2C%20%5B%2331352%5D%28https%3A//github.com/langgenius/dify/issues/31352%29%2C%20%5B%2331542%5D%28https%3A//github.com/langgenius/dify/issues/31542%29%29.%0A%0AThere%20is%20no%20official%20workaround%20yet.%20Some%20users%20have%20had%20partial%20success%20by%20re-importing%20nodes%20or%20resetting%20variables%2C%20but%20these%20are%20not%20guaranteed%20fixes.%20If%20you%20enable%20%22Subscription%22%20on%20the%20LARK_TRIGGER%20and%20the%20event%20does%20not%20supply%20an%20output%20schema%2C%20the%20output%20variables%20panel%20will%20disappear%20and%20downstream%20nodes%20cannot%20reference%20trigger%20outputs%2C%20causing%20validation%20errors%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/31210%29%29.%20Keeping%20your%20plugin%20and%20Docker%20setup%20up%20to%20date%20and%20ensuring%20the%20subscription%20is%20correctly%20linked%20may%20help%20in%20some%20cases%2C%20but%20the%20limitation%20will%20persist%20until%20Dify%20adds%20persistent%20schema%20support%20for%20trigger%20outputs.%0A%0AIf%20you%20want%20to%20help%20maintainers%20prioritize%20a%20fix%2C%20sharing%20workflow%20exports%2C%20error%20logs%2C%20or%20detailed%20reproduction%20steps%20in%20the%20main%20Dify%20issues%20can%20be%20useful.%20You%20can%20track%20progress%20in%20%5Bissue%20%231542%5D%28https%3A//github.com/langgenius/dify/issues/1542%29%20and%20related%20threads.)&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/2535)
yindo commented 2026-02-16 10:21:08 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 3, 2026):

Hi @Linyilan-zz, thanks for opening this issue.

Why this is being closed

Dify issue tracking requires English-only issue title and description for consistent collaboration.

Next steps

Please open a new issue in English and include clear details so maintainers can help efficiently.

Thanks for understanding and for your support.

@crazywoola commented on GitHub (Feb 3, 2026): Hi @Linyilan-zz, thanks for opening this issue. ### Why this is being closed Dify issue tracking requires English-only issue title and description for consistent collaboration. ### Next steps Please open a new issue in English and include clear details so maintainers can help efficiently. Thanks for understanding and for your support.
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
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#963
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?