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

Improve Schedule Triggers debug #21179

New Issue
Closed
opened 2026-02-21 20:11:18 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 20:11:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Dec 19, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

It is very hard to debug workflows that are bound to Schedule triggers.
a button to simulate "next tick" would be appreciated

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @DavideDelbianco on GitHub (Dec 19, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. It is very hard to debug workflows that are bound to Schedule triggers. a button to simulate "next tick" would be appreciated ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:11:18 -05:00
yindo closed this issue 2026-02-21 20:11:18 -05:00
yindo commented 2026-02-21 20:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Dec 25, 2025):

because the trigger time?

@fatelei commented on GitHub (Dec 25, 2025): because the trigger time?
yindo commented 2026-02-21 20:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Dec 25, 2025):

Yes because you have to wait for the time to tick.
I know I could use a second trigger with a time set to the nearest minute, but if the workflow relies on the time value, it would be better to simulate the next tick time.

@DavideDelbianco commented on GitHub (Dec 25, 2025): Yes because you have to wait for the time to tick. I know I could use a second trigger with a time set to the nearest minute, but if the workflow relies on the time value, it would be better to simulate the next tick time.
yindo commented 2026-02-21 20:11:18 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 25, 2026):

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

Issue Summary:

  • You requested a feature to add a button that simulates the "next tick" in schedule-triggered workflows for easier debugging.
  • You clarified that while a workaround with a second trigger exists, simulating the next tick would better support workflows relying on time values.
  • There have been no contributions or updates toward resolving this feature request.

Next Steps:

  • Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue.
  • If I don’t hear back within 15 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 25, 2026): Hi, @DavideDelbianco. 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 requested a feature to add a button that simulates the "next tick" in schedule-triggered workflows for easier debugging. - You clarified that while a workaround with a second trigger exists, simulating the next tick would better support workflows relying on time values. - There have been no contributions or updates toward resolving this feature request. **Next Steps:** - Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue. - If I don’t hear back within 15 days, the issue will be automatically closed. Thank you 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 💪 enhancement
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#21179
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?