langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Failed to parse response from plugin daemon to PluginDaemonBasicResponse [list], url: plugin/e6770410-e853-48b0-b966-89eaf022173a/management/agent_strategies #491

New Issue
Closed
opened 2026-02-16 10:19:33 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:19:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @getecms on GitHub (Jul 28, 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.5.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

6391-5ae7a910dbcdd79c.js:83 GET http://192.168.14.62/console/api/workspaces/current/agent-providers 400 (BAD REQUEST)
Image

✔️ Expected Behavior

I want to incorporate a knowledge base into my work

❌ Actual Behavior

The following errors have been corrected in the workflow
6391-5ae7a910dbcdd79c.js:83
GET http://192.168.14.62/console/api/workspaces/current/agent-providers 400 (BAD REQUEST)
I have introduced a knowledge base, but the prompt words cannot be added to the context, and clicking the button has no effect

Originally created by @getecms on GitHub (Jul 28, 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.5.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 6391-5ae7a910dbcdd79c.js:83 GET http://192.168.14.62/console/api/workspaces/current/agent-providers 400 (BAD REQUEST) <img width="1722" height="840" alt="Image" src="https://github.com/user-attachments/assets/3ec0c3b7-ff17-402d-b4d6-fda2b4239133" /> ### ✔️ Expected Behavior I want to incorporate a knowledge base into my work ### ❌ Actual Behavior The following errors have been corrected in the workflow 6391-5ae7a910dbcdd79c.js:83 GET http://192.168.14.62/console/api/workspaces/current/agent-providers 400 (BAD REQUEST) I have introduced a knowledge base, but the prompt words cannot be added to the context, and clicking the button has no effect
yindo closed this issue 2026-02-16 10:19:33 -05:00
yindo commented 2026-02-16 10:19:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 28, 2025):

Hi @getecms! I'm Dosu and I’m helping the dify team.

The 400 (BAD REQUEST) error and the "Failed to parse response from plugin daemon to PluginDaemonBasicResponse [list]" message indicate that the plugin daemon's response at the agent_strategies endpoint doesn't match the strict schema Dify expects. The response must be a JSON object with code (int), message (str), and data (list of agent providers, each with nested declaration and strategies fields) source.

Common causes are missing or malformed fields in the plugin daemon's response, or a mismatch after recent updates (Dify 1.6.0/1.7.0 introduced stricter checks and new protocols). This can break downstream features like adding prompt words to the context.

To troubleshoot:

  1. Enable debug logging by setting LOG_LEVEL=DEBUG and optionally configure LOG_FILE to capture detailed logs source.
  2. Check the plugin daemon logs for the actual JSON response at the failing endpoint. Compare it to the expected schema: it must include code, message, and a data array where each item has declaration and strategies fields.
  3. If any required field is missing or incorrectly formatted, update your plugin daemon or its configuration to match the expected structure.

If the issue persists, sharing the actual plugin daemon response and relevant logs will help pinpoint the mismatch.

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 (Jul 28, 2025): <!-- Greeting --> Hi @getecms! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The 400 (BAD REQUEST) error and the "Failed to parse response from plugin daemon to PluginDaemonBasicResponse [list]" message indicate that the plugin daemon's response at the agent_strategies endpoint doesn't match the strict schema Dify expects. The response must be a JSON object with code (int), message (str), and data (list of agent providers, each with nested declaration and strategies fields) [source](https://github.com/langgenius/dify/blob/5c5f61b2aaeeb048deaa5730222a7591d000b600/api/core/plugin/entities/plugin_daemon.py). Common causes are missing or malformed fields in the plugin daemon's response, or a mismatch after recent updates (Dify 1.6.0/1.7.0 introduced stricter checks and new protocols). This can break downstream features like adding prompt words to the context. To troubleshoot: 1. Enable debug logging by setting `LOG_LEVEL=DEBUG` and optionally configure `LOG_FILE` to capture detailed logs [source](https://github.com/langgenius/dify/blob/5c5f61b2aaeeb048deaa5730222a7591d000b600/api/extensions/ext_logging.py). 2. Check the plugin daemon logs for the actual JSON response at the failing endpoint. Compare it to the expected schema: it must include code, message, and a data array where each item has declaration and strategies fields. 3. If any required field is missing or incorrectly formatted, update your plugin daemon or its configuration to match the expected structure. If the issue persists, sharing the actual plugin daemon response and relevant logs will help pinpoint the mismatch. <!-- 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/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/566bd093-3770-425e-8110-2dea109a20b7?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/23045)
yindo commented 2026-02-16 10:19:33 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 28, 2025):

This version seems a bit outdated. Please provide the plugin version. Regarding issues with the plugin, do not submit them to the main repository.

@crazywoola commented on GitHub (Jul 28, 2025): This version seems a bit outdated. Please provide the plugin version. Regarding issues with the plugin, do not submit them to the main repository.
yindo commented 2026-02-16 10:19:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 20, 2025):

Hi, @getecms. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a 400 Bad Request error on a self-hosted Dify v1.5.0 instance when accessing the agent-providers API.
  • This error prevents prompt words from being added to the knowledge base context.
  • The issue is likely caused by the plugin daemon's response not matching the expected strict JSON schema, possibly due to missing or malformed fields.
  • I suggested enabling debug logs and checking the plugin daemon response for troubleshooting.
  • The maintainer noted that your Dify version is outdated and requested the plugin version, advising to report plugin issues outside the main repository.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If no response is received, this issue will be automatically closed in 5 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 20, 2025): Hi, @getecms. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a 400 Bad Request error on a self-hosted Dify v1.5.0 instance when accessing the agent-providers API. - This error prevents prompt words from being added to the knowledge base context. - The issue is likely caused by the plugin daemon's response not matching the expected strict JSON schema, possibly due to missing or malformed fields. - I suggested enabling debug logs and checking the plugin daemon response for troubleshooting. - The maintainer noted that your Dify version is outdated and requested the plugin version, advising to report plugin issues outside the main repository. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If no response is received, this issue will be automatically closed in 5 days. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#491
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?