Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix `trigger_provider_refresh` task is being invoked frequently, consuming CPU resources. [3 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35677•Fetched 2026-04-30 06:45:46
View on GitHub
Comments
3
Participants
2
Timeline
6
Reactions
1
Author
eldoradoeleldoradoel
Participants
dosubot[bot]dosubot[bot]eldoradoeleldoradoel
Timeline (top)
commented ×3labeled ×2closed ×1

Code Example

worker-1            | 2026-04-29 14:02:40.009 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[094c65b7-dddb-471d-8377-e22d1c1ffa96] received
worker-1            | 2026-04-29 14:02:40.014 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[be27fc0a-4eab-4d07-a23f-c0c288ffb422] received
worker-1            | 2026-04-29 14:02:40.020 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[54192566-e3f1-426b-bb96-75973c19140a] received
worker-1            | 2026-04-29 14:02:40.022 INFO [Dummy-1] [pidbox.py:111]  - pidbox: Connected to redis://:**@redis:6379/1.
worker-1            | 2026-04-29 14:02:40.036 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[3dae5072-4e83-458b-876d-7d471ec1068b] received
worker-1            | 2026-04-29 14:02:40.042 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[2a9a5dee-0f67-4c8c-a9b5-52b7b755faf7] received
worker-1            | 2026-04-29 14:02:40.078 INFO [Dummy-2] [trigger_provider_refresh_task.py:65] b194777190405721b3a3930c7bf71154 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.079 INFO [Dummy-3] [trigger_provider_refresh_task.py:65] 0dd753615c3c53bdb111a8001c1226e8 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.080 INFO [Dummy-4] [trigger_provider_refresh_task.py:65] 9cbdfbdde9015133bd270e8c05011aa8 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.080 INFO [Dummy-5] [trigger_provider_refresh_task.py:65] c1bc39dd46f05e5eacf8daed395a39de - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.112 INFO [Dummy-2] [trace.py:128] b194777190405721b3a3930c7bf71154 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[be27fc0a-4eab-4d07-a23f-c0c288ffb422] succeeded in 0.09774106706026942s: None
worker-1            | 2026-04-29 14:02:40.138 INFO [Dummy-3] [trace.py:128] 0dd753615c3c53bdb111a8001c1226e8 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[3dae5072-4e83-458b-876d-7d471ec1068b] succeeded in 0.10132737690582871s: None
worker-1            | 2026-04-29 14:02:40.164 INFO [Dummy-4] [trace.py:128] 9cbdfbdde9015133bd270e8c05011aa8 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[54192566-e3f1-426b-bb96-75973c19140a] succeeded in 0.1358447849052027s: None
worker-1            | 2026-04-29 14:02:40.193 INFO [Dummy-5] [trace.py:128] c1bc39dd46f05e5eacf8daed395a39de - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[094c65b7-dddb-471d-8377-e22d1c1ffa96] succeeded in 0.18261040502693504s: None
worker-1            | 2026-04-29 14:02:40.194 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[97df40ec-821e-42e3-912c-bafa164d32bc] received
worker-1            | 2026-04-29 14:02:40.195 INFO [Dummy-6] [trigger_provider_refresh_task.py:65] 6daa9387bc5459408bac9e53af1ec962 - Trigger refresh scan start: due=0
RAW_BUFFERClick to expand / collapse

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.14.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

update to 1.14.0

✔️ Expected Behavior

trigger_provider_refresh is called once every minute.

❌ Actual Behavior

worker-1            | 2026-04-29 14:02:40.009 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[094c65b7-dddb-471d-8377-e22d1c1ffa96] received
worker-1            | 2026-04-29 14:02:40.014 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[be27fc0a-4eab-4d07-a23f-c0c288ffb422] received
worker-1            | 2026-04-29 14:02:40.020 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[54192566-e3f1-426b-bb96-75973c19140a] received
worker-1            | 2026-04-29 14:02:40.022 INFO [Dummy-1] [pidbox.py:111]  - pidbox: Connected to redis://:**@redis:6379/1.
worker-1            | 2026-04-29 14:02:40.036 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[3dae5072-4e83-458b-876d-7d471ec1068b] received
worker-1            | 2026-04-29 14:02:40.042 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[2a9a5dee-0f67-4c8c-a9b5-52b7b755faf7] received
worker-1            | 2026-04-29 14:02:40.078 INFO [Dummy-2] [trigger_provider_refresh_task.py:65] b194777190405721b3a3930c7bf71154 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.079 INFO [Dummy-3] [trigger_provider_refresh_task.py:65] 0dd753615c3c53bdb111a8001c1226e8 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.080 INFO [Dummy-4] [trigger_provider_refresh_task.py:65] 9cbdfbdde9015133bd270e8c05011aa8 - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.080 INFO [Dummy-5] [trigger_provider_refresh_task.py:65] c1bc39dd46f05e5eacf8daed395a39de - Trigger refresh scan start: due=0
worker-1            | 2026-04-29 14:02:40.112 INFO [Dummy-2] [trace.py:128] b194777190405721b3a3930c7bf71154 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[be27fc0a-4eab-4d07-a23f-c0c288ffb422] succeeded in 0.09774106706026942s: None
worker-1            | 2026-04-29 14:02:40.138 INFO [Dummy-3] [trace.py:128] 0dd753615c3c53bdb111a8001c1226e8 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[3dae5072-4e83-458b-876d-7d471ec1068b] succeeded in 0.10132737690582871s: None
worker-1            | 2026-04-29 14:02:40.164 INFO [Dummy-4] [trace.py:128] 9cbdfbdde9015133bd270e8c05011aa8 - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[54192566-e3f1-426b-bb96-75973c19140a] succeeded in 0.1358447849052027s: None
worker-1            | 2026-04-29 14:02:40.193 INFO [Dummy-5] [trace.py:128] c1bc39dd46f05e5eacf8daed395a39de - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[094c65b7-dddb-471d-8377-e22d1c1ffa96] succeeded in 0.18261040502693504s: None
worker-1            | 2026-04-29 14:02:40.194 INFO [MainThread] [strategy.py:161]  - Task schedule.trigger_provider_refresh_task.trigger_provider_refresh[97df40ec-821e-42e3-912c-bafa164d32bc] received
worker-1            | 2026-04-29 14:02:40.195 INFO [Dummy-6] [trigger_provider_refresh_task.py:65] 6daa9387bc5459408bac9e53af1ec962 - Trigger refresh scan start: due=0

extent analysis

TL;DR

The trigger_provider_refresh task is being called multiple times instead of once every minute, indicating a potential scheduling issue.

Guidance

  • Review the scheduling configuration for trigger_provider_refresh_task to ensure it is set to run once every minute.
  • Check the logs for any errors or warnings related to task scheduling or execution.
  • Verify that the trigger_provider_refresh task is not being triggered manually or by another process.
  • Investigate the use of multiple worker threads (e.g., Dummy-1, Dummy-2, etc.) and their potential impact on task scheduling.

Example

No code snippet is provided as the issue seems to be related to task scheduling and configuration rather than code.

Notes

The provided logs indicate that multiple tasks are being received and executed in quick succession, which may be causing the issue. However, without more information about the scheduling configuration and task execution, it is difficult to provide a definitive solution.

Recommendation

Apply a workaround to adjust the scheduling configuration for trigger_provider_refresh_task to ensure it runs once every minute, and monitor the logs to verify the fix.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#API routing#API middleware#SSR setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING