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

Failed to invoke model qwen-flash, status code:401 #21460

New Issue
Open
opened 2026-02-21 20:12:39 -05:00 by yindo · 38 comments
yindo commented 2026-02-21 20:12:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @xuya227939 on GitHub (Jan 6, 2026).

Originally assigned to: @laipz8200 on GitHub.

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

Cloud or Self Hosted

Cloud

Steps to reproduce

I set up a workflow and called qwen3 flash. After running it for a while, it prompted me that the apikey was incorrect. However, the apikey can be run on the Tongyi Qianwen official website with a certain quota and no problem with permissions.

✔️ Expected Behavior

api-key is working.

Image

❌ Actual Behavior

No response

Originally created by @xuya227939 on GitHub (Jan 6, 2026). Originally assigned to: @laipz8200 on GitHub. ### 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.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce I set up a workflow and called qwen3 flash. After running it for a while, it prompted me that the apikey was incorrect. However, the apikey can be run on the Tongyi Qianwen official website with a certain quota and no problem with permissions. ### ✔️ Expected Behavior api-key is working. <img width="2058" height="1194" alt="Image" src="https://github.com/user-attachments/assets/e9d788ca-9b08-4c72-9347-6358ef30cab3" /> ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugcloud labels 2026-02-21 20:12:39 -05:00
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

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

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

A 401 error with qwen-flash in Dify Cloud almost always means the API key is being rejected during authentication, even if it works on the official provider site. The most common causes are: invisible characters or extra spaces in the key, using the wrong endpoint (domestic vs international), not updating the key in Dify after regenerating it, or plugin bugs related to credential caching or agent node memory. Double-check that your API key is in the correct format (usually starts with sk-), is pasted without any extra spaces, and that the endpoint toggle matches your key type. If you recently changed or regenerated your key, update it in Dify and save again. Avoid using the international endpoint unless your key specifically requires it. If you’re using agent nodes with memory, try disabling memory or switching agent strategies, as there are known plugin bugs that can cause unstable validation in cloud environments. For persistent issues, check Dify Cloud logs for backend error details—sometimes network instability or upstream API changes can also cause this error, even if the key is valid elsewhere. More troubleshooting details and workarounds are available in these threads: 1, 2, 3.

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 6, 2026): <!-- Greeting --> Hi @xuya227939! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> A 401 error with qwen-flash in Dify Cloud almost always means the API key is being rejected during authentication, even if it works on the official provider site. The most common causes are: invisible characters or extra spaces in the key, using the wrong endpoint (domestic vs international), not updating the key in Dify after regenerating it, or plugin bugs related to credential caching or agent node memory. Double-check that your API key is in the correct format (usually starts with `sk-`), is pasted without any extra spaces, and that the endpoint toggle matches your key type. If you recently changed or regenerated your key, update it in Dify and save again. Avoid using the international endpoint unless your key specifically requires it. If you’re using agent nodes with memory, try disabling memory or switching agent strategies, as there are known plugin bugs that can cause unstable validation in cloud environments. For persistent issues, check Dify Cloud logs for backend error details—sometimes network instability or upstream API changes can also cause this error, even if the key is valid elsewhere. More troubleshooting details and workarounds are available in these threads: [1](https://github.com/langgenius/dify/issues/27692), [2](https://github.com/langgenius/dify/issues/29538), [3](https://github.com/langgenius/dify/issues/23887). <!-- 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/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4f87f3b6-37a2-476c-b64e-dc584fcb6cab?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=A%20401%20error%20with%20qwen-flash%20in%20Dify%20Cloud%20almost%20always%20means%20the%20API%20key%20is%20being%20rejected%20during%20authentication%2C%20even%20if%20it%20works%20on%20the%20official%20provider%20site.%20The%20most%20common%20causes%20are%3A%20invisible%20characters%20or%20extra%20spaces%20in%20the%20key%2C%20using%20the%20wrong%20endpoint%20%28domestic%20vs%20international%29%2C%20not%20updating%20the%20key%20in%20Dify%20after%20regenerating%20it%2C%20or%20plugin%20bugs%20related%20to%20credential%20caching%20or%20agent%20node%20memory.%20Double-check%20that%20your%20API%20key%20is%20in%20the%20correct%20format%20%28usually%20starts%20with%20%60sk-%60%29%2C%20is%20pasted%20without%20any%20extra%20spaces%2C%20and%20that%20the%20endpoint%20toggle%20matches%20your%20key%20type.%20If%20you%20recently%20changed%20or%20regenerated%20your%20key%2C%20update%20it%20in%20Dify%20and%20save%20again.%20Avoid%20using%20the%20international%20endpoint%20unless%20your%20key%20specifically%20requires%20it.%20If%20you%E2%80%99re%20using%20agent%20nodes%20with%20memory%2C%20try%20disabling%20memory%20or%20switching%20agent%20strategies%2C%20as%20there%20are%20known%20plugin%20bugs%20that%20can%20cause%20unstable%20validation%20in%20cloud%20environments.%20For%20persistent%20issues%2C%20check%20Dify%20Cloud%20logs%20for%20backend%20error%20details%E2%80%94sometimes%20network%20instability%20or%20upstream%20API%20changes%20can%20also%20cause%20this%20error%2C%20even%20if%20the%20key%20is%20valid%20elsewhere.%20More%20troubleshooting%20details%20and%20workarounds%20are%20available%20in%20these%20threads%3A%20%5B1%5D%28https%3A//github.com/langgenius/dify/issues/27692%29%2C%20%5B2%5D%28https%3A//github.com/langgenius/dify/issues/29538%29%2C%20%5B3%5D%28https%3A//github.com/langgenius/dify/issues/23887%29.)&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/30611)
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 6, 2026):

you api key is wrong, please check it

@fatelei commented on GitHub (Jan 6, 2026): you api key is wrong, please check it
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 7, 2026):

I haven't changed anything, the configuration is ready again today, bro

@xuya227939 commented on GitHub (Jan 7, 2026): I haven't changed anything, the configuration is ready again today, bro
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 13, 2026):

Image

My first reply was normal, but my second reply reported an error, Can you tell me what the problem is? @fatelei

@xuya227939 commented on GitHub (Jan 13, 2026): <img width="1936" height="1296" alt="Image" src="https://github.com/user-attachments/assets/ae0b370d-fa2f-4ae7-bb6a-cf6035136479" /> My first reply was normal, but my second reply reported an error, Can you tell me what the problem is? @fatelei
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 13, 2026):

Image My first reply was normal, but my second reply reported an error, Can you tell me what the problem is? [@fatelei](https://github.com/fatelei)

i later try it

@fatelei commented on GitHub (Jan 13, 2026): > <img alt="Image" width="1936" height="1296" src="https://private-user-images.githubusercontent.com/16217324/535394803-ae0b370d-fa2f-4ae7-bb6a-cf6035136479.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjgzNjEyNjYsIm5iZiI6MTc2ODM2MDk2NiwicGF0aCI6Ii8xNjIxNzMyNC81MzUzOTQ4MDMtYWUwYjM3MGQtZmEyZi00YWU3LWJiNmEtY2Y2MDM1MTM2NDc5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAxMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMTE0VDAzMjI0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM5YTA1NTNhOWE4NzRlNGUxOWRkYWIyYzE1NGQ0ZDkwNzZmNGU0NzM4YjQ4ZDc0YjViNzE0NGZiMDdkNmQ0NWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.uRwYcg6vEPTufO04EwYE8Ue4AMcFesZvBpdwPaaJ3sw"> > My first reply was normal, but my second reply reported an error, Can you tell me what the problem is? [@fatelei](https://github.com/fatelei) i later try it
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

How's it going? This problem has occurred multiple times @fatelei

@xuya227939 commented on GitHub (Jan 14, 2026): How's it going? This problem has occurred multiple times @fatelei
yindo commented 2026-02-21 20:12:39 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

How's it going? This problem has occurred multiple times @fatelei

Image

i try it, it is no problem

@fatelei commented on GitHub (Jan 14, 2026): > How's it going? This problem has occurred multiple times [@fatelei](https://github.com/fatelei) <img width="2706" height="1760" alt="Image" src="https://github.com/user-attachments/assets/a0286b7e-4425-4a30-a3d5-7c4563a31182" /> i try it, it is no problem
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

Image

use qwen-3-flash, also no problem

@fatelei commented on GitHub (Jan 14, 2026): <img width="1050" height="1568" alt="Image" src="https://github.com/user-attachments/assets/0bcb2e82-45f6-4ecb-94ee-4bf0e81a0757" /> use qwen-3-flash, also no problem
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

Image

no problem

@fatelei commented on GitHub (Jan 14, 2026): <img width="2628" height="2008" alt="Image" src="https://github.com/user-attachments/assets/a072b18b-87ac-4115-bcf7-bf9a50434b11" /> no problem
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

perhaps you can create a new api key

@fatelei commented on GitHub (Jan 14, 2026): perhaps you can create a new api key
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

@xuya227939 commented on GitHub (Jan 14, 2026): This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

@fatelei commented on GitHub (Jan 14, 2026): > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) submit your dsl, i test with your dsl
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

@xuya227939 commented on GitHub (Jan 14, 2026): f399333d-2d64-4dab-be52-c65138726ac7 > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > submit your dsl, i test with your dsl
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

@fatelei commented on GitHub (Jan 14, 2026): > f399333d-2d64-4dab-be52-c65138726ac7 > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > submit your dsl, i test with your dsl you dsl file, you can export it
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

@xuya227939 commented on GitHub (Jan 14, 2026): > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > submit your dsl, i test with your dsl > > you dsl file, you can export it [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml)
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

ok

@fatelei commented on GitHub (Jan 14, 2026): > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > you dsl file, you can export it > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) ok
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

https://github.com/user-attachments/assets/358a7175-1eb5-417d-a495-dcae1375eba5

there is no problem

@fatelei commented on GitHub (Jan 14, 2026): > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > you dsl file, you can export it > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) https://github.com/user-attachments/assets/358a7175-1eb5-417d-a495-dcae1375eba5 there is no problem
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

Image

This is the interesting part. I can test it myself now. Let me show you our recording logs

Image Image
@xuya227939 commented on GitHub (Jan 14, 2026): <img width="1486" height="1282" alt="Image" src="https://github.com/user-attachments/assets/9a72d37e-604d-4ab4-898c-e6315ac9040f" /> This is the interesting part. I can test it myself now. Let me show you our recording logs <img width="2888" height="954" alt="Image" src="https://github.com/user-attachments/assets/0b8beebe-e0d4-44ae-8d6c-749fdb372d0a" /> <img width="2862" height="796" alt="Image" src="https://github.com/user-attachments/assets/260f76a3-90e8-476e-ad0e-a7298ecfaf66" />
yindo commented 2026-02-21 20:12:40 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

Screen.Recording.2026-01-14.at.20.09.45.mov
there is no problem

{
  "config": {
    "env": {},
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "allowAbsoluteUrls": true,
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "headers": {
      "Accept": "text/event-stream",
      "Content-Type": "application/json",
      "Cache-Control": "no-cache",
      "Connection": "keep-alive",
      "Authorization": "****************"
    },
    "method": "post",
    "url": "https://api.dify.ai/v1/chat-messages",
    "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}",
    "timeout": 0,
    "maxContentLength": -1,
    "maxBodyLength": -1
  },
  "level": "error",
  "message": "Request failed with status code 400",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 400\n    at AxiosError.from (index.js:5100:14)\n    at index.js:6801:32\n    at async Axios.request (index.js:7028:14)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at Axios.request (index.js:7032:41)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at async dispatch (index.js:2562:17)\n    at async timing2 (index.js:4509:5)",
  "code": "ERR_BAD_REQUEST",
  "status": 400,
  "$workers": {
    "truncated": false,
    "event": {
      "request": {
        "url": "https://api-service.net.cn/api/ai/chat-messages",
        "method": "POST",
        "path": "/api/ai/chat-messages"
      }
    },
    "outcome": "ok",
    "scriptName": "bookkeeping",
    "eventType": "fetch",
    "executionModel": "stateless",
    "scriptVersion": {
      "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63"
    },
    "requestId": "9bdc19e60ab85639"
  },
  "$metadata": {
    "id": "01KEXXAWV0X1Q0KY87DPVNN3GE",
    "requestId": "9bdc19e60ab85639",
    "trigger": "POST /api/ai/chat-messages",
    "service": "bookkeeping",
    "level": "error",
    "error": "Request failed with status code 400",
    "message": "Request failed with status code 400",
    "account": "cfe682662f84b68d09a53896c1fe7083",
    "type": "cf-worker",
    "fingerprint": "08418f03c2035b4fef3b04314f2f9514",
    "origin": "fetch",
    "messageTemplate": "Request failed with status code 400"
  }
}

error_log

@xuya227939 commented on GitHub (Jan 14, 2026): > > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > > > > you dsl file, you can export it > > > > > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) > > Screen.Recording.2026-01-14.at.20.09.45.mov > there is no problem ``` { "config": { "env": {}, "transitional": { "silentJSONParsing": true, "forcedJSONParsing": true, "clarifyTimeoutError": false }, "allowAbsoluteUrls": true, "adapter": [ "xhr", "http", "fetch" ], "xsrfCookieName": "XSRF-TOKEN", "xsrfHeaderName": "X-XSRF-TOKEN", "headers": { "Accept": "text/event-stream", "Content-Type": "application/json", "Cache-Control": "no-cache", "Connection": "keep-alive", "Authorization": "****************" }, "method": "post", "url": "https://api.dify.ai/v1/chat-messages", "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}", "timeout": 0, "maxContentLength": -1, "maxBodyLength": -1 }, "level": "error", "message": "Request failed with status code 400", "name": "AxiosError", "stack": "AxiosError: Request failed with status code 400\n at AxiosError.from (index.js:5100:14)\n at index.js:6801:32\n at async Axios.request (index.js:7028:14)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at Axios.request (index.js:7032:41)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at async dispatch (index.js:2562:17)\n at async timing2 (index.js:4509:5)", "code": "ERR_BAD_REQUEST", "status": 400, "$workers": { "truncated": false, "event": { "request": { "url": "https://api-service.net.cn/api/ai/chat-messages", "method": "POST", "path": "/api/ai/chat-messages" } }, "outcome": "ok", "scriptName": "bookkeeping", "eventType": "fetch", "executionModel": "stateless", "scriptVersion": { "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63" }, "requestId": "9bdc19e60ab85639" }, "$metadata": { "id": "01KEXXAWV0X1Q0KY87DPVNN3GE", "requestId": "9bdc19e60ab85639", "trigger": "POST /api/ai/chat-messages", "service": "bookkeeping", "level": "error", "error": "Request failed with status code 400", "message": "Request failed with status code 400", "account": "cfe682662f84b68d09a53896c1fe7083", "type": "cf-worker", "fingerprint": "08418f03c2035b4fef3b04314f2f9514", "origin": "fetch", "messageTemplate": "Request failed with status code 400" } } ``` error_log
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 14, 2026):

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

Screen.Recording.2026-01-14.at.20.09.45.mov
there is no problem

{
  "config": {
    "env": {},
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "allowAbsoluteUrls": true,
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "headers": {
      "Accept": "text/event-stream",
      "Content-Type": "application/json",
      "Cache-Control": "no-cache",
      "Connection": "keep-alive",
      "Authorization": "****************"
    },
    "method": "post",
    "url": "https://api.dify.ai/v1/chat-messages",
    "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}",
    "timeout": 0,
    "maxContentLength": -1,
    "maxBodyLength": -1
  },
  "level": "error",
  "message": "Request failed with status code 400",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 400\n    at AxiosError.from (index.js:5100:14)\n    at index.js:6801:32\n    at async Axios.request (index.js:7028:14)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at Axios.request (index.js:7032:41)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at async dispatch (index.js:2562:17)\n    at async timing2 (index.js:4509:5)",
  "code": "ERR_BAD_REQUEST",
  "status": 400,
  "$workers": {
    "truncated": false,
    "event": {
      "request": {
        "url": "https://api-service.net.cn/api/ai/chat-messages",
        "method": "POST",
        "path": "/api/ai/chat-messages"
      }
    },
    "outcome": "ok",
    "scriptName": "bookkeeping",
    "eventType": "fetch",
    "executionModel": "stateless",
    "scriptVersion": {
      "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63"
    },
    "requestId": "9bdc19e60ab85639"
  },
  "$metadata": {
    "id": "01KEXXAWV0X1Q0KY87DPVNN3GE",
    "requestId": "9bdc19e60ab85639",
    "trigger": "POST /api/ai/chat-messages",
    "service": "bookkeeping",
    "level": "error",
    "error": "Request failed with status code 400",
    "message": "Request failed with status code 400",
    "account": "cfe682662f84b68d09a53896c1fe7083",
    "type": "cf-worker",
    "fingerprint": "08418f03c2035b4fef3b04314f2f9514",
    "origin": "fetch",
    "messageTemplate": "Request failed with status code 400"
  }
}

error_log

this is frontend log, do you have backend log ?

@fatelei commented on GitHub (Jan 14, 2026): > > > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > > > > > > > you dsl file, you can export it > > > > > > > > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) > > > > > > Screen.Recording.2026-01-14.at.20.09.45.mov > > there is no problem > > ``` > { > "config": { > "env": {}, > "transitional": { > "silentJSONParsing": true, > "forcedJSONParsing": true, > "clarifyTimeoutError": false > }, > "allowAbsoluteUrls": true, > "adapter": [ > "xhr", > "http", > "fetch" > ], > "xsrfCookieName": "XSRF-TOKEN", > "xsrfHeaderName": "X-XSRF-TOKEN", > "headers": { > "Accept": "text/event-stream", > "Content-Type": "application/json", > "Cache-Control": "no-cache", > "Connection": "keep-alive", > "Authorization": "****************" > }, > "method": "post", > "url": "https://api.dify.ai/v1/chat-messages", > "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}", > "timeout": 0, > "maxContentLength": -1, > "maxBodyLength": -1 > }, > "level": "error", > "message": "Request failed with status code 400", > "name": "AxiosError", > "stack": "AxiosError: Request failed with status code 400\n at AxiosError.from (index.js:5100:14)\n at index.js:6801:32\n at async Axios.request (index.js:7028:14)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at Axios.request (index.js:7032:41)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at async dispatch (index.js:2562:17)\n at async timing2 (index.js:4509:5)", > "code": "ERR_BAD_REQUEST", > "status": 400, > "$workers": { > "truncated": false, > "event": { > "request": { > "url": "https://api-service.net.cn/api/ai/chat-messages", > "method": "POST", > "path": "/api/ai/chat-messages" > } > }, > "outcome": "ok", > "scriptName": "bookkeeping", > "eventType": "fetch", > "executionModel": "stateless", > "scriptVersion": { > "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63" > }, > "requestId": "9bdc19e60ab85639" > }, > "$metadata": { > "id": "01KEXXAWV0X1Q0KY87DPVNN3GE", > "requestId": "9bdc19e60ab85639", > "trigger": "POST /api/ai/chat-messages", > "service": "bookkeeping", > "level": "error", > "error": "Request failed with status code 400", > "message": "Request failed with status code 400", > "account": "cfe682662f84b68d09a53896c1fe7083", > "type": "cf-worker", > "fingerprint": "08418f03c2035b4fef3b04314f2f9514", > "origin": "fetch", > "messageTemplate": "Request failed with status code 400" > } > } > ``` > > error_log this is frontend log, do you have backend log ?
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 14, 2026):

What do you mean by backend logs

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

Screen.Recording.2026-01-14.at.20.09.45.mov
there is no problem

{
  "config": {
    "env": {},
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "allowAbsoluteUrls": true,
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "headers": {
      "Accept": "text/event-stream",
      "Content-Type": "application/json",
      "Cache-Control": "no-cache",
      "Connection": "keep-alive",
      "Authorization": "****************"
    },
    "method": "post",
    "url": "https://api.dify.ai/v1/chat-messages",
    "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}",
    "timeout": 0,
    "maxContentLength": -1,
    "maxBodyLength": -1
  },
  "level": "error",
  "message": "Request failed with status code 400",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 400\n    at AxiosError.from (index.js:5100:14)\n    at index.js:6801:32\n    at async Axios.request (index.js:7028:14)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at Axios.request (index.js:7032:41)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at async dispatch (index.js:2562:17)\n    at async timing2 (index.js:4509:5)",
  "code": "ERR_BAD_REQUEST",
  "status": 400,
  "$workers": {
    "truncated": false,
    "event": {
      "request": {
        "url": "https://api-service.net.cn/api/ai/chat-messages",
        "method": "POST",
        "path": "/api/ai/chat-messages"
      }
    },
    "outcome": "ok",
    "scriptName": "bookkeeping",
    "eventType": "fetch",
    "executionModel": "stateless",
    "scriptVersion": {
      "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63"
    },
    "requestId": "9bdc19e60ab85639"
  },
  "$metadata": {
    "id": "01KEXXAWV0X1Q0KY87DPVNN3GE",
    "requestId": "9bdc19e60ab85639",
    "trigger": "POST /api/ai/chat-messages",
    "service": "bookkeeping",
    "level": "error",
    "error": "Request failed with status code 400",
    "message": "Request failed with status code 400",
    "account": "cfe682662f84b68d09a53896c1fe7083",
    "type": "cf-worker",
    "fingerprint": "08418f03c2035b4fef3b04314f2f9514",
    "origin": "fetch",
    "messageTemplate": "Request failed with status code 400"
  }
}

error_log

this is frontend log, do you have backend log ?

@xuya227939 commented on GitHub (Jan 14, 2026): What do you mean by backend logs > > > > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > > > > > > > > > > you dsl file, you can export it > > > > > > > > > > > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) > > > > > > > > > Screen.Recording.2026-01-14.at.20.09.45.mov > > > there is no problem > > > > > > ``` > > { > > "config": { > > "env": {}, > > "transitional": { > > "silentJSONParsing": true, > > "forcedJSONParsing": true, > > "clarifyTimeoutError": false > > }, > > "allowAbsoluteUrls": true, > > "adapter": [ > > "xhr", > > "http", > > "fetch" > > ], > > "xsrfCookieName": "XSRF-TOKEN", > > "xsrfHeaderName": "X-XSRF-TOKEN", > > "headers": { > > "Accept": "text/event-stream", > > "Content-Type": "application/json", > > "Cache-Control": "no-cache", > > "Connection": "keep-alive", > > "Authorization": "****************" > > }, > > "method": "post", > > "url": "https://api.dify.ai/v1/chat-messages", > > "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}", > > "timeout": 0, > > "maxContentLength": -1, > > "maxBodyLength": -1 > > }, > > "level": "error", > > "message": "Request failed with status code 400", > > "name": "AxiosError", > > "stack": "AxiosError: Request failed with status code 400\n at AxiosError.from (index.js:5100:14)\n at index.js:6801:32\n at async Axios.request (index.js:7028:14)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at Axios.request (index.js:7032:41)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at async dispatch (index.js:2562:17)\n at async timing2 (index.js:4509:5)", > > "code": "ERR_BAD_REQUEST", > > "status": 400, > > "$workers": { > > "truncated": false, > > "event": { > > "request": { > > "url": "https://api-service.net.cn/api/ai/chat-messages", > > "method": "POST", > > "path": "/api/ai/chat-messages" > > } > > }, > > "outcome": "ok", > > "scriptName": "bookkeeping", > > "eventType": "fetch", > > "executionModel": "stateless", > > "scriptVersion": { > > "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63" > > }, > > "requestId": "9bdc19e60ab85639" > > }, > > "$metadata": { > > "id": "01KEXXAWV0X1Q0KY87DPVNN3GE", > > "requestId": "9bdc19e60ab85639", > > "trigger": "POST /api/ai/chat-messages", > > "service": "bookkeeping", > > "level": "error", > > "error": "Request failed with status code 400", > > "message": "Request failed with status code 400", > > "account": "cfe682662f84b68d09a53896c1fe7083", > > "type": "cf-worker", > > "fingerprint": "08418f03c2035b4fef3b04314f2f9514", > > "origin": "fetch", > > "messageTemplate": "Request failed with status code 400" > > } > > } > > ``` > > > > > > > > > > > > > > > > > > > > > > > > error_log > > this is frontend log, do you have backend log ?
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Jan 15, 2026):

What do you mean by backend logs

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

Screen.Recording.2026-01-14.at.20.09.45.mov
there is no problem

{
  "config": {
    "env": {},
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "allowAbsoluteUrls": true,
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "headers": {
      "Accept": "text/event-stream",
      "Content-Type": "application/json",
      "Cache-Control": "no-cache",
      "Connection": "keep-alive",
      "Authorization": "****************"
    },
    "method": "post",
    "url": "https://api.dify.ai/v1/chat-messages",
    "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}",
    "timeout": 0,
    "maxContentLength": -1,
    "maxBodyLength": -1
  },
  "level": "error",
  "message": "Request failed with status code 400",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 400\n    at AxiosError.from (index.js:5100:14)\n    at index.js:6801:32\n    at async Axios.request (index.js:7028:14)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at Axios.request (index.js:7032:41)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at async dispatch (index.js:2562:17)\n    at async timing2 (index.js:4509:5)",
  "code": "ERR_BAD_REQUEST",
  "status": 400,
  "$workers": {
    "truncated": false,
    "event": {
      "request": {
        "url": "https://api-service.net.cn/api/ai/chat-messages",
        "method": "POST",
        "path": "/api/ai/chat-messages"
      }
    },
    "outcome": "ok",
    "scriptName": "bookkeeping",
    "eventType": "fetch",
    "executionModel": "stateless",
    "scriptVersion": {
      "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63"
    },
    "requestId": "9bdc19e60ab85639"
  },
  "$metadata": {
    "id": "01KEXXAWV0X1Q0KY87DPVNN3GE",
    "requestId": "9bdc19e60ab85639",
    "trigger": "POST /api/ai/chat-messages",
    "service": "bookkeeping",
    "level": "error",
    "error": "Request failed with status code 400",
    "message": "Request failed with status code 400",
    "account": "cfe682662f84b68d09a53896c1fe7083",
    "type": "cf-worker",
    "fingerprint": "08418f03c2035b4fef3b04314f2f9514",
    "origin": "fetch",
    "messageTemplate": "Request failed with status code 400"
  }
}

error_log

this is frontend log, do you have backend log ?

if you use the docker, docker logs -f docker-api-1

@fatelei commented on GitHub (Jan 15, 2026): > What do you mean by backend logs > > > > > > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > > > > > > > > > > > > > you dsl file, you can export it > > > > > > > > > > > > > > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) > > > > > > > > > > > > Screen.Recording.2026-01-14.at.20.09.45.mov > > > > there is no problem > > > > > > > > > ``` > > > { > > > "config": { > > > "env": {}, > > > "transitional": { > > > "silentJSONParsing": true, > > > "forcedJSONParsing": true, > > > "clarifyTimeoutError": false > > > }, > > > "allowAbsoluteUrls": true, > > > "adapter": [ > > > "xhr", > > > "http", > > > "fetch" > > > ], > > > "xsrfCookieName": "XSRF-TOKEN", > > > "xsrfHeaderName": "X-XSRF-TOKEN", > > > "headers": { > > > "Accept": "text/event-stream", > > > "Content-Type": "application/json", > > > "Cache-Control": "no-cache", > > > "Connection": "keep-alive", > > > "Authorization": "****************" > > > }, > > > "method": "post", > > > "url": "https://api.dify.ai/v1/chat-messages", > > > "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}", > > > "timeout": 0, > > > "maxContentLength": -1, > > > "maxBodyLength": -1 > > > }, > > > "level": "error", > > > "message": "Request failed with status code 400", > > > "name": "AxiosError", > > > "stack": "AxiosError: Request failed with status code 400\n at AxiosError.from (index.js:5100:14)\n at index.js:6801:32\n at async Axios.request (index.js:7028:14)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at Axios.request (index.js:7032:41)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at async dispatch (index.js:2562:17)\n at async timing2 (index.js:4509:5)", > > > "code": "ERR_BAD_REQUEST", > > > "status": 400, > > > "$workers": { > > > "truncated": false, > > > "event": { > > > "request": { > > > "url": "https://api-service.net.cn/api/ai/chat-messages", > > > "method": "POST", > > > "path": "/api/ai/chat-messages" > > > } > > > }, > > > "outcome": "ok", > > > "scriptName": "bookkeeping", > > > "eventType": "fetch", > > > "executionModel": "stateless", > > > "scriptVersion": { > > > "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63" > > > }, > > > "requestId": "9bdc19e60ab85639" > > > }, > > > "$metadata": { > > > "id": "01KEXXAWV0X1Q0KY87DPVNN3GE", > > > "requestId": "9bdc19e60ab85639", > > > "trigger": "POST /api/ai/chat-messages", > > > "service": "bookkeeping", > > > "level": "error", > > > "error": "Request failed with status code 400", > > > "message": "Request failed with status code 400", > > > "account": "cfe682662f84b68d09a53896c1fe7083", > > > "type": "cf-worker", > > > "fingerprint": "08418f03c2035b4fef3b04314f2f9514", > > > "origin": "fetch", > > > "messageTemplate": "Request failed with status code 400" > > > } > > > } > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > error_log > > > > > > this is frontend log, do you have backend log ? if you use the docker, docker logs -f docker-api-1
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 15, 2026):

I did not deploy using Docker, I used the dify cloud service

What do you mean by backend logs

f399333d-2d64-4dab-be52-c65138726ac7

This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared @fatelei

submit your dsl, i test with your dsl

you dsl file, you can export it

AI 记账.yml

Screen.Recording.2026-01-14.at.20.09.45.mov
there is no problem

{
  "config": {
    "env": {},
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "allowAbsoluteUrls": true,
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "headers": {
      "Accept": "text/event-stream",
      "Content-Type": "application/json",
      "Cache-Control": "no-cache",
      "Connection": "keep-alive",
      "Authorization": "****************"
    },
    "method": "post",
    "url": "https://api.dify.ai/v1/chat-messages",
    "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}",
    "timeout": 0,
    "maxContentLength": -1,
    "maxBodyLength": -1
  },
  "level": "error",
  "message": "Request failed with status code 400",
  "name": "AxiosError",
  "stack": "AxiosError: Request failed with status code 400\n    at AxiosError.from (index.js:5100:14)\n    at index.js:6801:32\n    at async Axios.request (index.js:7028:14)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at Axios.request (index.js:7032:41)\n    at async index.js:7470:22\n    at async dispatch (index.js:2562:17)\n    at async cors2 (index.js:4229:5)\n    at async dispatch (index.js:2562:17)\n    at async secureHeaders2 (index.js:4382:5)\n    at async dispatch (index.js:2562:17)\n    at async prettyJSON2 (index.js:4577:5)\n    at async dispatch (index.js:2562:17)\n    at async timing2 (index.js:4509:5)",
  "code": "ERR_BAD_REQUEST",
  "status": 400,
  "$workers": {
    "truncated": false,
    "event": {
      "request": {
        "url": "https://api-service.net.cn/api/ai/chat-messages",
        "method": "POST",
        "path": "/api/ai/chat-messages"
      }
    },
    "outcome": "ok",
    "scriptName": "bookkeeping",
    "eventType": "fetch",
    "executionModel": "stateless",
    "scriptVersion": {
      "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63"
    },
    "requestId": "9bdc19e60ab85639"
  },
  "$metadata": {
    "id": "01KEXXAWV0X1Q0KY87DPVNN3GE",
    "requestId": "9bdc19e60ab85639",
    "trigger": "POST /api/ai/chat-messages",
    "service": "bookkeeping",
    "level": "error",
    "error": "Request failed with status code 400",
    "message": "Request failed with status code 400",
    "account": "cfe682662f84b68d09a53896c1fe7083",
    "type": "cf-worker",
    "fingerprint": "08418f03c2035b4fef3b04314f2f9514",
    "origin": "fetch",
    "messageTemplate": "Request failed with status code 400"
  }
}

error_log

this is frontend log, do you have backend log ?

@xuya227939 commented on GitHub (Jan 15, 2026): I did not deploy using Docker, I used the dify cloud service > What do you mean by backend logs > > > > > > > > f399333d-2d64-4dab-be52-c65138726ac7 > > > > > > > > > This is the problem. I also created a new apiKey before and used it for a few days without any issues. However, after a few days, this problem appeared [@fatelei](https://github.com/fatelei) > > > > > > > > > > > > > > > > > > > > > > > > submit your dsl, i test with your dsl > > > > > > > > > > > > > > > > > > you dsl file, you can export it > > > > > > > > > > > > > > > [AI 记账.yml](https://github.com/user-attachments/files/24612700/AI.yml) > > > > > > > > > > > > Screen.Recording.2026-01-14.at.20.09.45.mov > > > > there is no problem > > > > > > > > > ``` > > > { > > > "config": { > > > "env": {}, > > > "transitional": { > > > "silentJSONParsing": true, > > > "forcedJSONParsing": true, > > > "clarifyTimeoutError": false > > > }, > > > "allowAbsoluteUrls": true, > > > "adapter": [ > > > "xhr", > > > "http", > > > "fetch" > > > ], > > > "xsrfCookieName": "XSRF-TOKEN", > > > "xsrfHeaderName": "X-XSRF-TOKEN", > > > "headers": { > > > "Accept": "text/event-stream", > > > "Content-Type": "application/json", > > > "Cache-Control": "no-cache", > > > "Connection": "keep-alive", > > > "Authorization": "****************" > > > }, > > > "method": "post", > > > "url": "https://api.dify.ai/v1/chat-messages", > > > "data": "{\"inputs\":{},\"user\":\"1263507e-c34d-4636-ae6f-4ec83bf2eabc\",\"response_mode\":\"blocking\",\"query\":\"多的, date:2026-01-14, incomeClassification:工资、兼职、奖金、生活费、理财、红包、自定义, expenseCategory:餐饮、日用品、交通、蔬菜、水果、零食、娱乐、通讯、服饰、住房、小孩、长辈、旅行、医疗、宠物、礼物、办公、购物、美容、学习、游戏、运动、自定义,ai_username:live管家,user_name:主人,ai_role:记账管家,ai_personality:精通理财,温文尔雅\",\"conversation_id\":\"f353da00-5025-4e0f-9e52-904caea2ad8a\"}", > > > "timeout": 0, > > > "maxContentLength": -1, > > > "maxBodyLength": -1 > > > }, > > > "level": "error", > > > "message": "Request failed with status code 400", > > > "name": "AxiosError", > > > "stack": "AxiosError: Request failed with status code 400\n at AxiosError.from (index.js:5100:14)\n at index.js:6801:32\n at async Axios.request (index.js:7028:14)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at Axios.request (index.js:7032:41)\n at async index.js:7470:22\n at async dispatch (index.js:2562:17)\n at async cors2 (index.js:4229:5)\n at async dispatch (index.js:2562:17)\n at async secureHeaders2 (index.js:4382:5)\n at async dispatch (index.js:2562:17)\n at async prettyJSON2 (index.js:4577:5)\n at async dispatch (index.js:2562:17)\n at async timing2 (index.js:4509:5)", > > > "code": "ERR_BAD_REQUEST", > > > "status": 400, > > > "$workers": { > > > "truncated": false, > > > "event": { > > > "request": { > > > "url": "https://api-service.net.cn/api/ai/chat-messages", > > > "method": "POST", > > > "path": "/api/ai/chat-messages" > > > } > > > }, > > > "outcome": "ok", > > > "scriptName": "bookkeeping", > > > "eventType": "fetch", > > > "executionModel": "stateless", > > > "scriptVersion": { > > > "id": "9cb18d88-ff7e-4f65-b04d-061cb6596b63" > > > }, > > > "requestId": "9bdc19e60ab85639" > > > }, > > > "$metadata": { > > > "id": "01KEXXAWV0X1Q0KY87DPVNN3GE", > > > "requestId": "9bdc19e60ab85639", > > > "trigger": "POST /api/ai/chat-messages", > > > "service": "bookkeeping", > > > "level": "error", > > > "error": "Request failed with status code 400", > > > "message": "Request failed with status code 400", > > > "account": "cfe682662f84b68d09a53896c1fe7083", > > > "type": "cf-worker", > > > "fingerprint": "08418f03c2035b4fef3b04314f2f9514", > > > "origin": "fetch", > > > "messageTemplate": "Request failed with status code 400" > > > } > > > } > > > ``` > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > error_log > > > > > > this is frontend log, do you have backend log ?
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 16, 2026):

@fatelei bro,I haven't changed anything, it's better now. There must be something wrong with you guys

@xuya227939 commented on GitHub (Jan 16, 2026): @fatelei bro,I haven't changed anything, it's better now. There must be something wrong with you guys
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 22, 2026):

@xuya227939

Sorry for the late reply. I have some ideas on how to solve this. Could you let me know which version of the plugin you're using?

@laipz8200 commented on GitHub (Jan 22, 2026): @xuya227939 Sorry for the late reply. I have some ideas on how to solve this. Could you let me know which version of the plugin you're using?
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 22, 2026):

I have been using it on the cloud all along, and as you can see in the reply above, exporting DLS and everything else is normal. After copying the same application on my end, after a few hours, there will be apiKey failure @laipz8200

@xuya227939 commented on GitHub (Jan 22, 2026): I have been using it on the cloud all along, and as you can see in the reply above, exporting DLS and everything else is normal. After copying the same application on my end, after a few hours, there will be apiKey failure @laipz8200
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 22, 2026):

After deployment, a few hours later, this issue will be reported, the apiKey is invalid, an issue will be raised, and the two people will have 24 conversations, but there will be no response afterwards.

Logically speaking, a project of this size (star 127k) should not have such a low quality issue.

Then, I replicated a project again, and after a few hours, the apiKey failed again, using a cloud solution.

Later, when I deployed the Docker solution, Nima and the Docker deployment documentation were all incorrect... Pnpm&node version error, unable to start. PNPM run build has been unresponsive.

Image Image Image Image Image

@laipz8200

@xuya227939 commented on GitHub (Jan 22, 2026): After deployment, a few hours later, this issue will be reported, the apiKey is invalid, an issue will be raised, and the two people will have 24 conversations, but there will be no response afterwards. Logically speaking, a project of this size (star 127k) should not have such a low quality issue. Then, I replicated a project again, and after a few hours, the apiKey failed again, using a cloud solution. Later, when I deployed the Docker solution, Nima and the Docker deployment documentation were all incorrect... Pnpm&node version error, unable to start. PNPM run build has been unresponsive. <img width="1936" height="1296" alt="Image" src="https://github.com/user-attachments/assets/bb0d86f8-e570-4347-ad32-7f6ec0f811c0" /> <img width="2888" height="954" alt="Image" src="https://github.com/user-attachments/assets/ded1399f-780b-4c8b-b1a9-c25a9a15151d" /> <img width="2058" height="1194" alt="Image" src="https://github.com/user-attachments/assets/287471d1-09d3-445e-b67a-3ce42e4d9a6f" /> <img width="1068" height="798" alt="Image" src="https://github.com/user-attachments/assets/141bd6f1-5dfb-4722-9f37-51ea0f528c6d" /> <img width="1530" height="1006" alt="Image" src="https://github.com/user-attachments/assets/c037f0a3-32bb-43f6-9002-d5a8976113b7" /> @laipz8200
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 22, 2026):

@xuya227939 I’m sorry for the confusion; this issue is likely related to how our “Tongyi” plugin is implemented.

If you have a moment, could you please follow these steps:

  1. Open the Plugins tab in the top-right corner of the Dify main interface.
  2. Find the “Tongyi” plugin there and let us know which version you’re using.
  3. If it’s not on the latest version, update it to see if that resolves the issue.
Image
@laipz8200 commented on GitHub (Jan 22, 2026): @xuya227939 I’m sorry for the confusion; this issue is likely related to how our “Tongyi” plugin is implemented. If you have a moment, could you please follow these steps: 1. Open the Plugins tab in the top-right corner of the Dify main interface. 2. Find the “Tongyi” plugin there and let us know which version you’re using. 3. If it’s not on the latest version, update it to see if that resolves the issue. <img width="591" height="113" alt="Image" src="https://github.com/user-attachments/assets/05babd36-bfdc-4eca-9d25-6e1d021e3392" />
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 22, 2026):

Maybe related: https://github.com/langgenius/dify-official-plugins/issues/2182

@laipz8200 commented on GitHub (Jan 22, 2026): Maybe related: https://github.com/langgenius/dify-official-plugins/issues/2182
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 22, 2026):

Image

@laipz8200

@xuya227939 commented on GitHub (Jan 22, 2026): <img width="758" height="424" alt="Image" src="https://github.com/user-attachments/assets/cfcd5008-bfb6-4533-a3d8-b0cf2feb9b38" /> @laipz8200
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 22, 2026):

可能相关：langgenius/dify-official-plugins#2182

Image

I did not use the international node @laipz8200

@xuya227939 commented on GitHub (Jan 22, 2026): > 可能相关：[langgenius/dify-official-plugins#2182](https://github.com/langgenius/dify-official-plugins/issues/2182) <img width="1666" height="880" alt="Image" src="https://github.com/user-attachments/assets/33ca170e-bb36-4060-bfbf-b9a42f8bb810" /> I did not use the international node @laipz8200
yindo commented 2026-02-21 20:12:41 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 22, 2026):

@xuya227939 Thank you for the information. We need some time to investigate the cause of this issue. In the meantime, you are welcome to use OpenAI-compatible models to access Qwen if needed.

@laipz8200 commented on GitHub (Jan 22, 2026): @xuya227939 Thank you for the information. We need some time to investigate the cause of this issue. In the meantime, you are welcome to use OpenAI-compatible models to access Qwen if needed.
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 22, 2026):

@laipz8200 Please give me an approximate time to solve the problem, as it has seriously affected the customer

@xuya227939 commented on GitHub (Jan 22, 2026): @laipz8200 Please give me an approximate time to solve the problem, as it has seriously affected the customer
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@laipz8200 commented on GitHub (Jan 23, 2026):

Hi @xuya227939.

Please click your avatar in Dify Cloud, and select Support then Contact Us to reach our customer support team.

This will allow us to access your account details and provide you with better service.

@laipz8200 commented on GitHub (Jan 23, 2026): Hi @xuya227939. Please click your avatar in Dify Cloud, and select `Support` then `Contact Us` to reach our customer support team. This will allow us to access your account details and provide you with better service.
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 23, 2026):

Image This ? @laipz8200

@xuya227939 commented on GitHub (Jan 23, 2026): <img width="894" height="752" alt="Image" src="https://github.com/user-attachments/assets/12fbd226-95b0-4eed-865d-fa16e8261706" /> This ? @laipz8200
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 23, 2026):

@xuya227939 Thank you for the information. We need some time to investigate the cause of this issue. In the meantime, you are welcome to use OpenAI-compatible models to access Qwen if needed.

How should I use it? I used the qwen flash from Tongyi Qianwen to configure the apiKey and baseURL of GPT, but received an error message

@laipz8200

@xuya227939 commented on GitHub (Jan 23, 2026): > [@xuya227939](https://github.com/xuya227939) Thank you for the information. We need some time to investigate the cause of this issue. In the meantime, you are welcome to use OpenAI-compatible models to access Qwen if needed. How should I use it? I used the qwen flash from Tongyi Qianwen to configure the apiKey and baseURL of GPT, but received an error message @laipz8200
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@Stream29 commented on GitHub (Jan 23, 2026):

This issue should be fixed with: https://github.com/langgenius/dify-official-plugins/pull/2473.

@Stream29 commented on GitHub (Jan 23, 2026): This issue should be fixed with: https://github.com/langgenius/dify-official-plugins/pull/2473.
yindo commented 2026-02-21 20:12:42 -05:00
Author
Owner
Copy Link
Copy Source

@xuya227939 commented on GitHub (Jan 23, 2026):

This issue should be fixed with: langgenius/dify-official-plugins#2473.

Copy that, thank you, sir. @fatelei @laipz8200 @Stream29

@xuya227939 commented on GitHub (Jan 23, 2026): > This issue should be fixed with: [langgenius/dify-official-plugins#2473](https://github.com/langgenius/dify-official-plugins/pull/2473). Copy that, thank you, sir. @fatelei @laipz8200 @Stream29
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#21460
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?