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

[PR #24039] feat: comprehensive trigger node system with Schedule Trigger implementation #30483

New Issue
Closed
opened 2026-02-21 20:47:35 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:47:35 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/24039

State: closed
Merged: Yes

Related #24001
Related #23981

Summary

Implements the foundational architecture for trigger-based workflow nodes, introducing three new trigger types and a conditional Start tab system.

Changes:

  • Add 3 trigger node types: Schedule, Webhook, Plugin
  • Implement conditional Start tab in block selector (shows only trigger nodes)
  • Add workflow entry point abstraction with trigger priority
  • Integrate export functionality into More Actions dropdown

Current Limitations

  • Start node exclusion: Due to code constraints, the traditional Start node (User Input) cannot appear in the Start tab currently
  • No uniqueness constraint: All entry nodes (triggers + start) lack global uniqueness enforcement - multiple entry nodes can exist simultaneously
  • Placeholder implementations: Schedule/Webhook/Plugin panels show placeholder content only
  • Missing Test Run: Preview button not yet replaced with Test Run dropdown

Next Steps

  • Implement Schedule Trigger configuration panel
  • Add Test Run functionality
  • Enforce entry node uniqueness constraints
  • Include User Input in Start tab

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/24039 **State:** closed **Merged:** Yes --- Related #24001 Related #23981 ## Summary Implements the foundational architecture for trigger-based workflow nodes, introducing three new trigger types and a conditional Start tab system. **Changes:** - Add 3 trigger node types: Schedule, Webhook, Plugin - Implement conditional Start tab in block selector (shows only trigger nodes) - Add workflow entry point abstraction with trigger priority - Integrate export functionality into More Actions dropdown ## Current Limitations - **Start node exclusion**: Due to code constraints, the traditional Start node (User Input) cannot appear in the Start tab currently - **No uniqueness constraint**: All entry nodes (triggers + start) lack global uniqueness enforcement - multiple entry nodes can exist simultaneously - **Placeholder implementations**: Schedule/Webhook/Plugin panels show placeholder content only - **Missing Test Run**: Preview button not yet replaced with Test Run dropdown ## Next Steps - Implement Schedule Trigger configuration panel - Add Test Run functionality - Enforce entry node uniqueness constraints - Include User Input in Start tab ## Checklist - [x] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:47:35 -05:00
yindo closed this issue 2026-02-21 20:47:35 -05:00
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 pull-request
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#30483
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?