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

Unable to have a normal conversation with the agent in the chat box after token expiration #6835

New Issue
Closed
opened 2026-02-21 18:17:32 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:17:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @llinvokerl on GitHub (Nov 19, 2024).

Originally assigned to: @zxhlyh on GitHub.

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.2

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. Modify the environment variable ACCESS_TOKEN_EXPIRE_MINUTES to "1", so the access token will expire in 1 minute.
  2. Enter the agent's Debug and Preview interface and send a message, triggering the /chat-messages API.
  3. Wait 1 minute for the token to expire, then send another message, calling /chat-messages again.

After completing the steps mentioned above, the browser starts an infinite loop, alternately calling /refresh-token and /chat-messages, while the chat box continually shows the agent as "speaking."

This issue occurs because, after the frontend receives a 401 unauthorized response from the /chat-messages call, it requests a token refresh. However, when it calls /chat-messages again, it doesn't use the new token. Since the old token has expired, it still gets a 401 unauthorized response from /chat-messages. As a result, the frontend keeps requesting /refresh-token, but this effort is in vain.

✔️ Expected Behavior

image
After using /refresh-token, it's necessary to explicitly use the updated token when calling /chat-messages again.

❌ Actual Behavior

image
image
image

Originally created by @llinvokerl on GitHub (Nov 19, 2024). Originally assigned to: @zxhlyh on GitHub. ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.11.2 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce 1. Modify the environment variable ACCESS_TOKEN_EXPIRE_MINUTES to "1", so the access token will expire in 1 minute. 2. Enter the agent's Debug and Preview interface and send a message, triggering the /chat-messages API. 3. Wait 1 minute for the token to expire, then send another message, calling /chat-messages again. After completing the steps mentioned above, the browser starts an infinite loop, alternately calling /refresh-token and /chat-messages, while the chat box continually shows the agent as "speaking." This issue occurs because, after the frontend receives a 401 unauthorized response from the /chat-messages call, it requests a token refresh. However, when it calls /chat-messages again, it doesn't use the new token. Since the old token has expired, it still gets a 401 unauthorized response from /chat-messages. As a result, the frontend keeps requesting /refresh-token, but this effort is in vain. ### ✔️ Expected Behavior ![image](https://github.com/user-attachments/assets/988c54f5-e9f0-4ab8-bb92-ef60787989da) After using /refresh-token, it's necessary to explicitly use the updated token when calling /chat-messages again. ### ❌ Actual Behavior ![image](https://github.com/user-attachments/assets/99217637-c6ff-4382-89d6-469305d64810) ![image](https://github.com/user-attachments/assets/3820d0e4-4db4-41b8-b44b-edc5e836ca1b) ![image](https://github.com/user-attachments/assets/7b28f3bc-31e9-418f-81cf-b91f5a0e138c)
yindo added the 🐞 bug label 2026-02-21 18:17:32 -05:00
yindo closed this issue 2026-02-21 18:17:32 -05:00
yindo commented 2026-02-21 18:17:33 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 19, 2024):

To resolve the issue where the chat box enters an infinite loop of calling /refresh-token and /chat-messages after token expiration, ensure that the new token is being used for subsequent requests after a successful token refresh. Here are some steps to consider:

  1. Update Token Usage: After obtaining a new access token, make sure it is updated in local storage and used for all subsequent API requests. Verify that the code correctly updates the console_token and refresh_token in local storage and that these updated tokens are used in the headers of the /chat-messages API call.

  2. Check 401 Responses: If a 401 response is received after a token refresh, ensure that the new token is being used. If the old token is still being used, it will lead to repeated token refresh attempts.

  3. Avoid Infinite Loops: Ensure that the token refresh logic is separate from the main fetch logic to prevent it from triggering another refresh inadvertently. This separation helps avoid infinite loops.

  4. Debugging: Add logging or debugging statements to confirm that the new token is being set and used correctly in the /chat-messages request.

  5. Error Handling: Implement error handling to manage cases where the token refresh fails, such as prompting the user to re-login if necessary.

These steps should help in resolving the issue by ensuring that the new token is correctly utilized after a refresh [1].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 19, 2024): <!-- Answer --> To resolve the issue where the chat box enters an infinite loop of calling `/refresh-token` and `/chat-messages` after token expiration, ensure that the new token is being used for subsequent requests after a successful token refresh. Here are some steps to consider: 1. **Update Token Usage**: After obtaining a new access token, make sure it is updated in local storage and used for all subsequent API requests. Verify that the code correctly updates the `console_token` and `refresh_token` in local storage and that these updated tokens are used in the headers of the `/chat-messages` API call. 2. **Check 401 Responses**: If a 401 response is received after a token refresh, ensure that the new token is being used. If the old token is still being used, it will lead to repeated token refresh attempts. 3. **Avoid Infinite Loops**: Ensure that the token refresh logic is separate from the main fetch logic to prevent it from triggering another refresh inadvertently. This separation helps avoid infinite loops. 4. **Debugging**: Add logging or debugging statements to confirm that the new token is being set and used correctly in the `/chat-messages` request. 5. **Error Handling**: Implement error handling to manage cases where the token refresh fails, such as prompting the user to re-login if necessary. These steps should help in resolving the issue by ensuring that the new token is correctly utilized after a refresh <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/service/refresh-token.ts)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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 🐞 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#6835
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?