langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The newly added MCP service, code changes have modified the interface description of the MCP, and the modification has already been made in the MCP, but the previous interface description is still displayed in the studio. #21828

New Issue
Open
opened 2026-02-21 20:14:30 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:14:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @enniszhou on GitHub (Jan 21, 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.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The newly added MCP service, code changes have modified the interface description of the MCP, and the modification has already been made in the MCP, but the previous interface description is still displayed in the studio.

mcp api description：
Image

Studio api description： error
Image

✔️ Expected Behavior

The interface descriptions in the studio and MCP remain consistent.

❌ Actual Behavior

No response

Originally created by @enniszhou on GitHub (Jan 21, 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.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The newly added MCP service, code changes have modified the interface description of the MCP, and the modification has already been made in the MCP, but the previous interface description is still displayed in the studio. mcp api description： <img width="1899" height="927" alt="Image" src="https://github.com/user-attachments/assets/f7046a98-9c8c-4a0f-ae04-939dbea049d8" /> Studio api description： error <img width="1905" height="926" alt="Image" src="https://github.com/user-attachments/assets/a8cdcc91-7862-46b7-8ec6-6e8146dcd7d1" /> ### ✔️ Expected Behavior The interface descriptions in the studio and MCP remain consistent. ### ❌ Actual Behavior _No response_
yindo added the 🐞 buggood first issue labels 2026-02-21 20:14:30 -05:00
yindo commented 2026-02-21 20:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 21, 2026):

This is a known issue in Dify v1.11.1: when you update the MCP interface description, the Studio UI may still show the old version due to backend Redis caching. The tool provider list API uses a 5-minute cache, and changes (auth, create, update, delete) don't always trigger cache invalidation, so the Studio displays stale data until the cache expires or is refreshed. This affects MCP, API, workflow, and builtin tools details.

Workarounds for v1.11.1:

  • Manually clear the Redis cache or restart backend services to force a refresh details.
  • Edit and save the MCP provider again in the Studio; this can trigger a refresh in some cases details.
  • Make sure all MCP tool descriptions are non-null in the database (tool_mcp_providers table); missing descriptions can cause tools to disappear or not update details.

This bug was fixed in later versions by ensuring cache invalidation after MCP provider changes (see PRs #29960, #29972, #30150, #30159). Upgrading to a version with these fixes will resolve the problem.

The Studio frontend always fetches tool/interface descriptions from the backend API; it does not cache them itself. If the backend cache is stale, the UI will show outdated info until the backend cache is refreshed code reference.

Troubleshooting checklist:

  1. Try restarting backend services or clearing Redis cache.
  2. Edit and save the MCP provider again.
  3. Check your database for null tool descriptions and update if needed.
  4. Consider upgrading to a newer Dify version if possible.

Let me know if you need details on how to perform any of these steps.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 21, 2026): <!-- Answer --> This is a known issue in Dify v1.11.1: when you update the MCP interface description, the Studio UI may still show the old version due to backend Redis caching. The tool provider list API uses a 5-minute cache, and changes (auth, create, update, delete) don't always trigger cache invalidation, so the Studio displays stale data until the cache expires or is refreshed. This affects MCP, API, workflow, and builtin tools [details](https://github.com/langgenius/dify/issues/30322). Workarounds for v1.11.1: - Manually clear the Redis cache or restart backend services to force a refresh [details](https://github.com/langgenius/dify/issues/29971). - Edit and save the MCP provider again in the Studio; this can trigger a refresh in some cases [details](https://github.com/langgenius/dify/issues/29987). - Make sure all MCP tool descriptions are non-null in the database (`tool_mcp_providers` table); missing descriptions can cause tools to disappear or not update [details](https://github.com/langgenius/dify/issues/22179). This bug was fixed in later versions by ensuring cache invalidation after MCP provider changes (see PRs [#29960](https://github.com/langgenius/dify/pull/29960), [#29972](https://github.com/langgenius/dify/pull/29972), [#30150](https://github.com/langgenius/dify/pull/30150), [#30159](https://github.com/langgenius/dify/pull/30159)). Upgrading to a version with these fixes will resolve the problem. The Studio frontend always fetches tool/interface descriptions from the backend API; it does not cache them itself. If the backend cache is stale, the UI will show outdated info until the backend cache is refreshed [code reference](https://github.com/langgenius/dify/blob/211c57f7b62fe3578c77fcb00aebc5760e8e5466/web/service/tools.ts#L1-L143). Troubleshooting checklist: 1. Try restarting backend services or clearing Redis cache. 2. Edit and save the MCP provider again. 3. Check your database for null tool descriptions and update if needed. 4. Consider upgrading to a newer Dify version if possible. Let me know if you need details on how to perform any of these steps. <!-- 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/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fd338d08-43e8-469f-bfeb-beaef4c2af8d?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20in%20Dify%20v1.11.1%3A%20when%20you%20update%20the%20MCP%20interface%20description%2C%20the%20Studio%20UI%20may%20still%20show%20the%20old%20version%20due%20to%20backend%20Redis%20caching.%20The%20tool%20provider%20list%20API%20uses%20a%205-minute%20cache%2C%20and%20changes%20%28auth%2C%20create%2C%20update%2C%20delete%29%20don%27t%20always%20trigger%20cache%20invalidation%2C%20so%20the%20Studio%20displays%20stale%20data%20until%20the%20cache%20expires%20or%20is%20refreshed.%20This%20affects%20MCP%2C%20API%2C%20workflow%2C%20and%20builtin%20tools%20%5Bdetails%5D%28https%3A//github.com/langgenius/dify/issues/30322%29.%0A%0AWorkarounds%20for%20v1.11.1%3A%0A-%20Manually%20clear%20the%20Redis%20cache%20or%20restart%20backend%20services%20to%20force%20a%20refresh%20%5Bdetails%5D%28https%3A//github.com/langgenius/dify/issues/29971%29.%0A-%20Edit%20and%20save%20the%20MCP%20provider%20again%20in%20the%20Studio%3B%20this%20can%20trigger%20a%20refresh%20in%20some%20cases%20%5Bdetails%5D%28https%3A//github.com/langgenius/dify/issues/29987%29.%0A-%20Make%20sure%20all%20MCP%20tool%20descriptions%20are%20non-null%20in%20the%20database%20%28%60tool_mcp_providers%60%20table%29%3B%20missing%20descriptions%20can%20cause%20tools%20to%20disappear%20or%20not%20update%20%5Bdetails%5D%28https%3A//github.com/langgenius/dify/issues/22179%29.%0A%0AThis%20bug%20was%20fixed%20in%20later%20versions%20by%20ensuring%20cache%20invalidation%20after%20MCP%20provider%20changes%20%28see%20PRs%20%5B%2329960%5D%28https%3A//github.com/langgenius/dify/pull/29960%29%2C%20%5B%2329972%5D%28https%3A//github.com/langgenius/dify/pull/29972%29%2C%20%5B%2330150%5D%28https%3A//github.com/langgenius/dify/pull/30150%29%2C%20%5B%2330159%5D%28https%3A//github.com/langgenius/dify/pull/30159%29%29.%20Upgrading%20to%20a%20version%20with%20these%20fixes%20will%20resolve%20the%20problem.%0A%0AThe%20Studio%20frontend%20always%20fetches%20tool/interface%20descriptions%20from%20the%20backend%20API%3B%20it%20does%20not%20cache%20them%20itself.%20If%20the%20backend%20cache%20is%20stale%2C%20the%20UI%20will%20show%20outdated%20info%20until%20the%20backend%20cache%20is%20refreshed%20%5Bcode%20reference%5D%28https%3A//github.com/langgenius/dify/blob/211c57f7b62fe3578c77fcb00aebc5760e8e5466/web/service/tools.ts%23L1-L143%29.%0A%0ATroubleshooting%20checklist%3A%0A1.%20Try%20restarting%20backend%20services%20or%20clearing%20Redis%20cache.%0A2.%20Edit%20and%20save%20the%20MCP%20provider%20again.%0A3.%20Check%20your%20database%20for%20null%20tool%20descriptions%20and%20update%20if%20needed.%0A4.%20Consider%20upgrading%20to%20a%20newer%20Dify%20version%20if%20possible.%0A%0ALet%20me%20know%20if%20you%20need%20details%20on%20how%20to%20perform%20any%20of%20these%20steps.)&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/31372)
yindo commented 2026-02-21 20:14:30 -05:00
Author
Owner
Copy Link
Copy Source

@shirsenduda commented on GitHub (Feb 20, 2026):

All tasks completed, CI is green. Ready for review when you have time! Thanks.

@shirsenduda commented on GitHub (Feb 20, 2026): All tasks completed, CI is green. Ready for review when you have time! Thanks.
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 good first issue 🐞 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#21828
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?