langgenius / langgenius/dify

I clearly set the trigger to run every 10 minutes, but every 3–5 days, it automatically changes to every 2 minutes.

Open
#41,214 6 comments 1 reaction 0 assignees View on GitHub
🐞 bug
Dominant language
TypeScript
Stars
156k
Forks
24.6k
Avg merge
22h 9m
Merged PRs (30d)
610

Description

### 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

Version1.16.1

### Cloud or Self Hosted

Self Hosted (Docker)

### Steps to reproduce

Image

### ✔️ Expected Behavior

The trigger needs to be a little more stable.

### ❌ Actual Behavior

However, when I perform the following steps, it returns to normal, but after 3–5 days, the trigger still changes from once every 10 minutes to once every 2 minutes.
sudo docker compose -p dify down
sudo docker compose -p dify up -d

Contributor guide

Open the contributing guide

Research direction

Reproduce the trigger behavior on Dify 1.16.1 in the self-hosted Docker setup, using a 10-minute interval and observing it over several days. Compare the configured interval before and after the reported docker compose down/up restart; done means the trigger remains set to every 10 minutes without requiring a restart.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.