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

Run failed: Request to Plugin Daemon Service failed-500 #20044

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

Originally created by @highhead on GitHub (Oct 30, 2025).

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.9.2 latest

Cloud or Self Hosted

Cloud

Steps to reproduce

  • Suddenly "Run failed: Request to Plugin Daemon Service failed-500" error without any change on Chatflow
  • Chatbot timing out

✔️ Expected Behavior

No error.

❌ Actual Behavior

Run failed: Request to Plugin Daemon Service failed-500 and Timeouts.

Originally created by @highhead on GitHub (Oct 30, 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] 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.9.2 latest ### Cloud or Self Hosted Cloud ### Steps to reproduce * Suddenly "Run failed: Request to Plugin Daemon Service failed-500" error without any change on Chatflow * Chatbot timing out ### ✔️ Expected Behavior No error. ### ❌ Actual Behavior Run failed: Request to Plugin Daemon Service failed-500 and Timeouts.
yindo added the 🐞 bugcloud labels 2026-02-21 20:05:33 -05:00
yindo closed this issue 2026-02-21 20:05:33 -05:00
yindo commented 2026-02-21 20:05:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 30, 2025):

This error is actively tracked in the Dify repo and has affected multiple users on v1.9.2 cloud deployments, often causing chatbot timeouts and plugin failures without any user-side changes. Recent updates switched the HTTP client to httpx and added stricter timeouts for plugin daemon calls, which may be exposing or causing backend instability PR #26119, PR #26852.

Common causes for this error include backend service outages, network or DNS resolution issues between the API and Plugin Daemon Service, or misconfigured dependencies like Redis. In similar cases, users have resolved the issue by checking service health, ensuring correct Docker network and hostname configuration, and verifying that Redis is reachable from the plugin daemon container (not set to localhost) discussion.

If you have access to logs, look for connection errors, DNS failures, or Redis connectivity problems around the time of the 500 error. If the issue persists and you’re on the managed cloud, it’s likely a backend problem that requires maintainer intervention. For self-hosted setups, double-check your Docker Compose config for correct service names, ports, and environment variables.

This is a known issue and is under investigation by maintainers. If you have additional logs or context, sharing them in the open issue may help with diagnosis.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 30, 2025): <!-- Answer --> This error is actively tracked in the Dify repo and has affected multiple users on v1.9.2 cloud deployments, often causing chatbot timeouts and plugin failures without any user-side changes. Recent updates switched the HTTP client to `httpx` and added stricter timeouts for plugin daemon calls, which may be exposing or causing backend instability [PR #26119](https://github.com/langgenius/dify/pull/26119), [PR #26852](https://github.com/langgenius/dify/pull/26852). Common causes for this error include backend service outages, network or DNS resolution issues between the API and Plugin Daemon Service, or misconfigured dependencies like Redis. In similar cases, users have resolved the issue by checking service health, ensuring correct Docker network and hostname configuration, and verifying that Redis is reachable from the plugin daemon container (not set to `localhost`) [discussion](https://github.com/langgenius/dify/issues/18120#issuecomment-2807970984). If you have access to logs, look for connection errors, DNS failures, or Redis connectivity problems around the time of the 500 error. If the issue persists and you’re on the managed cloud, it’s likely a backend problem that requires maintainer intervention. For self-hosted setups, double-check your Docker Compose config for correct service names, ports, and environment variables. This is a known issue and is under investigation by maintainers. If you have additional logs or context, sharing them in the open issue may help with diagnosis. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/37b29a40-9383-49cf-80a5-882fe5d689fd?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27659)
yindo commented 2026-02-21 20:05:33 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (Oct 30, 2025):

Last successful run is logged 10/30/2025 10:17:51 AM CET so something broke between 10/30/2025 10:17:51 AM CET and 10/30/2025 11:14:51 AM CET

@highhead commented on GitHub (Oct 30, 2025): Last successful run is logged 10/30/2025 10:17:51 AM CET so something broke between 10/30/2025 10:17:51 AM CET and 10/30/2025 11:14:51 AM CET
yindo commented 2026-02-21 20:05:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 30, 2025):

Thanks for narrowing down the time window—this is really helpful for root cause analysis. Since no code or infrastructure changes were merged during that hour, the issue likely stems from a backend outage or instability, which matches similar reports from other cloud users on 1.9.2 around this period example.

For cloud deployments, the best way to correlate these 500 errors with backend events is to use integrated monitoring tools like Langfuse, LangSmith, Arize, or Weave. These platforms let you trace workflow and chatflow runs by start/end time, error status, and unique IDs, making it easier for maintainers to pinpoint exactly when and why failures occurred Langfuse docs, LangSmith docs, Arize docs, Weave docs.

If you have access to any workflow or chatflow logs, filtering by the provided time window (10:17:51–11:14:51 CET) and looking for error traces or status changes should help maintainers correlate your incident with backend logs and monitoring data. If you spot any error details or trace IDs, sharing those in the open issue will speed up diagnosis.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 30, 2025): <!-- Answer --> Thanks for narrowing down the time window—this is really helpful for root cause analysis. Since no code or infrastructure changes were merged during that hour, the issue likely stems from a backend outage or instability, which matches similar reports from other cloud users on 1.9.2 around this period [example](https://github.com/langgenius/dify/issues/27350). For cloud deployments, the best way to correlate these 500 errors with backend events is to use integrated monitoring tools like Langfuse, LangSmith, Arize, or Weave. These platforms let you trace workflow and chatflow runs by start/end time, error status, and unique IDs, making it easier for maintainers to pinpoint exactly when and why failures occurred [Langfuse docs](https://github.com/langgenius/dify-docs/blob/c975dd5571048c3c58444d1a6ac536b12ae165af/en/guides/monitoring/integrate-external-ops-tools/integrate-langfuse.mdx), [LangSmith docs](https://github.com/langgenius/dify-docs/blob/c975dd5571048c3c58444d1a6ac536b12ae165af/en/guides/monitoring/integrate-external-ops-tools/integrate-langsmith.mdx), [Arize docs](https://github.com/langgenius/dify-docs/blob/c975dd5571048c3c58444d1a6ac536b12ae165af/en/guides/monitoring/integrate-external-ops-tools/integrate-arize.mdx), [Weave docs](https://github.com/langgenius/dify-docs/blob/c975dd5571048c3c58444d1a6ac536b12ae165af/en/guides/monitoring/integrate-external-ops-tools/integrate-weave.mdx). If you have access to any workflow or chatflow logs, filtering by the provided time window (10:17:51–11:14:51 CET) and looking for error traces or status changes should help maintainers correlate your incident with backend logs and monitoring data. If you spot any error details or trace IDs, sharing those in the open issue will speed up diagnosis. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/dbaf1651-b56a-4128-a915-197a5fcb3014?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27659)
yindo commented 2026-02-21 20:05:34 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (Oct 30, 2025):

Seems like related to AWS Bedrock again:
OpenAI Models seem to work, but AWS Bedrock Anthropic Claude is broken with timeouts and the error above.

Update to AWS Bedrock Plugins 0.0.41 - 0.0.44 (latest) isn't an option as it still gives another error which is reported here (just tried with latest version):
https://github.com/langgenius/dify/issues/27361

Nothing we can do on our side! Please urgently take a look, as our customers cannot use our bots.

Example Apps: 43450cb2-7edd-4cee-82a6-ea83e506b150 and 95b82dd8-fb6c-4982-97e2-e43af48613e9 and 5d1ca903-ed14-4dba-8740-77958572ba2c

@highhead commented on GitHub (Oct 30, 2025): Seems like related to AWS Bedrock again: OpenAI Models seem to work, but AWS Bedrock Anthropic Claude is broken with timeouts and the error above. Update to AWS Bedrock Plugins 0.0.41 - 0.0.44 (latest) isn't an option as it still gives another error which is reported here (just tried with latest version): https://github.com/langgenius/dify/issues/27361 Nothing we can do on our side! Please urgently take a look, as our customers cannot use our bots. Example Apps: 43450cb2-7edd-4cee-82a6-ea83e506b150 and 95b82dd8-fb6c-4982-97e2-e43af48613e9 and 5d1ca903-ed14-4dba-8740-77958572ba2c
yindo commented 2026-02-21 20:05:34 -05:00
Author
Owner
Copy Link
Copy Source

@highhead commented on GitHub (Oct 30, 2025):

It suddenly works again, without any indication about the cause or the fix - could you please take a look what the issue was pretty please.

@highhead commented on GitHub (Oct 30, 2025): It suddenly works again, without any indication about the cause or the fix - could you please take a look what the issue was pretty please.
yindo commented 2026-02-21 20:05:34 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 30, 2025):

There’s no public post-mortem or maintainer update explaining the sudden fix, but based on similar incidents, the most likely causes are either a backend service restart, a hotfix applied by the Dify team, or recovery from an upstream AWS Bedrock or DNS outage. Previous issues with AWS Bedrock Claude models have resolved themselves after AWS-side incidents, and maintainers have confirmed that such outages can cause intermittent errors that disappear once AWS recovers or backend mitigations are applied (see here).

For the TimingContextRaceConditionError and related 500s, maintainers have acknowledged the bug and are investigating, but there’s no documented root cause or fix yet (see issue #27361). If you need a detailed post-mortem, you can request one in the open issue to help the team correlate your incident with backend logs. Otherwise, monitoring the linked issues is the best way to stay updated on any official explanations or fixes.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 30, 2025): <!-- Answer --> There’s no public post-mortem or maintainer update explaining the sudden fix, but based on similar incidents, the most likely causes are either a backend service restart, a hotfix applied by the Dify team, or recovery from an upstream AWS Bedrock or DNS outage. Previous issues with AWS Bedrock Claude models have resolved themselves after AWS-side incidents, and maintainers have confirmed that such outages can cause intermittent errors that disappear once AWS recovers or backend mitigations are applied ([see here](https://github.com/langgenius/dify/issues/27144)). For the TimingContextRaceConditionError and related 500s, maintainers have acknowledged the bug and are investigating, but there’s no documented root cause or fix yet ([see issue #27361](https://github.com/langgenius/dify/issues/27361)). If you need a detailed post-mortem, you can request one in the open issue to help the team correlate your incident with backend logs. Otherwise, monitoring the linked issues is the best way to stay updated on any official explanations or fixes. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e143f114-2ec6-43c7-b981-1317868b72c4?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27659)
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 cloud 🐞 bug
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#20044
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?