Does Dify's Scheduled Trigger support pause/stop operations? #22206

Closed
opened 2026-02-21 20:16:09 -05:00 by yindo · 1 comment
Owner

Originally created by @Zedthm on GitHub (Feb 12, 2026).

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-fix.1

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Hello, I am deploying applications based on the open-source version of Dify (version: [replace with your version, e.g., 0.6.10]). I have configured multiple scheduled triggers (e.g., scheduled knowledge base synchronization, scheduled AI inference task execution) and encountered a question during use:
When I need to temporarily terminate the execution of a specific scheduled trigger (e.g., incorrect task configuration, temporary suspension of execution) or permanently stop a trigger that is no longer needed, does Dify support pausing/stopping scheduled triggers directly?

✔️ Expected Behavior

force Scheduled Trigger stop

Actual Behavior

I did not find an obvious "Pause" button in the "Triggers/Scheduled Tasks" page of the application backend (remove this line if you actually saw it);
I considered modifying the trigger time (e.g., setting it to a future date) to achieve de facto suspension, but hope for a more official and straightforward method.
Expected outcomes:
Temporary stop: Retain trigger configurations, only pause execution, and allow one-click recovery later;
Permanent stop: Delete trigger configurations and terminate execution permanently.
Deployment Environment:
Deployment method: Docker/Containerized deployment (replace with your actual deployment method);
Dify version: Open-source edition v[x.x.x] (required, please fill in).

Originally created by @Zedthm on GitHub (Feb 12, 2026). ### 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-fix.1 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce Hello, I am deploying applications based on the open-source version of Dify (version: [replace with your version, e.g., 0.6.10]). I have configured multiple scheduled triggers (e.g., scheduled knowledge base synchronization, scheduled AI inference task execution) and encountered a question during use: When I need to temporarily terminate the execution of a specific scheduled trigger (e.g., incorrect task configuration, temporary suspension of execution) or permanently stop a trigger that is no longer needed, does Dify support pausing/stopping scheduled triggers directly? ### ✔️ Expected Behavior force Scheduled Trigger stop ### ❌ Actual Behavior I did not find an obvious "Pause" button in the "Triggers/Scheduled Tasks" page of the application backend (remove this line if you actually saw it); I considered modifying the trigger time (e.g., setting it to a future date) to achieve de facto suspension, but hope for a more official and straightforward method. Expected outcomes: Temporary stop: Retain trigger configurations, only pause execution, and allow one-click recovery later; Permanent stop: Delete trigger configurations and terminate execution permanently. Deployment Environment: Deployment method: Docker/Containerized deployment (replace with your actual deployment method); Dify version: Open-source edition v[x.x.x] (required, please fill in).
yindo added the 🙋‍♂️ question label 2026-02-21 20:16:09 -05:00
yindo closed this issue 2026-02-21 20:16:09 -05:00
Author
Owner

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

Hi @Zedthm, thanks for opening this issue.

Why this is being closed

This issue tracker is reserved for actionable bugs/tasks. This report looks like a usage question.

Next steps

Please use the community channels instead:

If this is actually a bug/task, please open a new issue with clear reproducible details.

Thanks for understanding and for supporting Dify.

@crazywoola commented on GitHub (Feb 12, 2026): Hi @Zedthm, thanks for opening this issue. ### Why this is being closed This issue tracker is reserved for actionable bugs/tasks. This report looks like a usage question. ### Next steps Please use the community channels instead: - https://forum.dify.ai/ - https://discord.com/invite/FngNHpbcY7 If this is actually a bug/task, please open a new issue with clear reproducible details. Thanks for understanding and for supporting Dify.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#22206