langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

When adding multiple scheduled triggers, they do not trigger correctly, but only one of them is triggered. #20748

New Issue
Open
opened 2026-02-21 20:08:47 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 20:08:47 -05:00
Owner
Copy Link
Copy Source

Originally created by @fsea on GitHub (Dec 2, 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.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image As shown in the picture above, three scheduled triggers were added, but in reality, only the one at 6:00 PM was triggered, and the other two were not triggered.

✔️ Expected Behavior

Trigger all timers normally

❌ Actual Behavior

Only one of the three was triggered

Originally created by @fsea on GitHub (Dec 2, 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.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1280" height="855" alt="Image" src="https://github.com/user-attachments/assets/06f83665-6977-4048-a9bf-a61c5a690cc9" /> As shown in the picture above, three scheduled triggers were added, but in reality, only the one at 6:00 PM was triggered, and the other two were not triggered. ### ✔️ Expected Behavior Trigger all timers normally ### ❌ Actual Behavior Only one of the three was triggered
yindo added the 🐞 bugstale labels 2026-02-21 20:08:47 -05:00
yindo commented 2026-02-21 20:08:47 -05:00
Author
Owner
Copy Link
Copy Source

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

Dify v1.10.1 only supports a single scheduled trigger per workflow. Even if you add multiple scheduled triggers, only the first one will be recognized and executed due to how the backend extracts and syncs schedule nodes from the workflow graph (source).

Recent updates (after v1.10.1) have added support for multiple start nodes and triggers working in parallel (source), so upgrading to a newer version will enable this feature. If upgrading isn't possible, you can split your workflow into multiple apps, each with its own scheduled trigger, or use external scheduling (like cron jobs or scripts) to call the workflow via API/webhook at the desired times.

If you want help with upgrading or workarounds, let me know!

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 2, 2025): <!-- Answer --> Dify v1.10.1 only supports a single scheduled trigger per workflow. Even if you add multiple scheduled triggers, only the first one will be recognized and executed due to how the backend extracts and syncs schedule nodes from the workflow graph ([source](https://github.com/langgenius/dify/blob/9b9588f20df3c4c0f650324c8c9a6f041233b4bb/api/services/trigger/schedule_service.py#L22-L313)). Recent updates (after v1.10.1) have added support for multiple start nodes and triggers working in parallel ([source](https://github.com/langgenius/dify/pull/24134)), so upgrading to a newer version will enable this feature. If upgrading isn't possible, you can split your workflow into multiple apps, each with its own scheduled trigger, or use external scheduling (like cron jobs or scripts) to call the workflow via API/webhook at the desired times. If you want help with upgrading or workarounds, let me know! <!-- 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/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/42fb81a6-3db0-4412-b624-2932d7826ca0?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Dify%20v1.10.1%20only%20supports%20a%20single%20scheduled%20trigger%20per%20workflow.%20Even%20if%20you%20add%20multiple%20scheduled%20triggers%2C%20only%20the%20first%20one%20will%20be%20recognized%20and%20executed%20due%20to%20how%20the%20backend%20extracts%20and%20syncs%20schedule%20nodes%20from%20the%20workflow%20graph%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/9b9588f20df3c4c0f650324c8c9a6f041233b4bb/api/services/trigger/schedule_service.py%23L22-L313%29%29.%20%0A%0ARecent%20updates%20%28after%20v1.10.1%29%20have%20added%20support%20for%20multiple%20start%20nodes%20and%20triggers%20working%20in%20parallel%20%28%5Bsource%5D%28https%3A//github.com/langgenius/dify/pull/24134%29%29%2C%20so%20upgrading%20to%20a%20newer%20version%20will%20enable%20this%20feature.%20If%20upgrading%20isn%27t%20possible%2C%20you%20can%20split%20your%20workflow%20into%20multiple%20apps%2C%20each%20with%20its%20own%20scheduled%20trigger%2C%20or%20use%20external%20scheduling%20%28like%20cron%20jobs%20or%20scripts%29%20to%20call%20the%20workflow%20via%20API/webhook%20at%20the%20desired%20times.%0A%0AIf%20you%20want%20help%20with%20upgrading%20or%20workarounds%2C%20let%20me%20know%21)&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/29038)
yindo commented 2026-02-21 20:08:47 -05:00
Author
Owner
Copy Link
Copy Source

@xb565517830 commented on GitHub (Dec 12, 2025):

After upgrading to version 1.11.1, adding multiple scheduled triggers only results in one being triggered.

@xb565517830 commented on GitHub (Dec 12, 2025): After upgrading to version 1.11.1, adding multiple scheduled triggers only results in one being triggered.
yindo commented 2026-02-21 20:08:47 -05:00
Author
Owner
Copy Link
Copy Source

@Yevanchen commented on GitHub (Jan 7, 2026):

My further question is whether multiple schedule nodes will subsequently affect the same business process or two completely unrelated branches？

@Yevanchen commented on GitHub (Jan 7, 2026): My further question is whether multiple schedule nodes will subsequently affect the same business process or two completely unrelated branches？
yindo commented 2026-02-21 20:08:47 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @fsea. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that in Dify v1.10.1, only one scheduled trigger (6:00 PM) activates despite adding multiple triggers.
  • It was clarified that v1.10.1 supports only a single scheduled trigger per workflow.
  • Versions after v1.10.1 enable multiple triggers in parallel.
  • Some users noted that even after upgrading to v1.11.1, only one trigger fires, leading to questions about multi-trigger behavior.
  • The recommended resolution is to upgrade beyond v1.10.1 or restructure workflows by splitting them or using external scheduling.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify; if so, you can keep the discussion open by commenting here.
  • Otherwise, I will automatically close this issue in 15 days.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 7, 2026): Hi, @fsea. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.10.1, only one scheduled trigger (6:00 PM) activates despite adding multiple triggers. - It was clarified that v1.10.1 supports only a single scheduled trigger per workflow. - Versions after v1.10.1 enable multiple triggers in parallel. - Some users noted that even after upgrading to v1.11.1, only one trigger fires, leading to questions about multi-trigger behavior. - The recommended resolution is to upgrade beyond v1.10.1 or restructure workflows by splitting them or using external scheduling. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify; if so, you can keep the discussion open by commenting here. - Otherwise, I will automatically close this issue in 15 days. Thanks for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label stale 🐞 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#20748
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?