[Bug]: LLMBundle.encode can't update token usage

[BadwomanCraZY]

Self Checks

• 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).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

26D3480E

RAGFlow image version

26D3480E(V0.12.1~174)

Other environment information

Actual behavior

i choose the embedding model, it can help me to cut chunks, but it cant analyse.
with the log like:
LLMBundle.encode can't update token usage for d8bcb636087e11f093fa022937737b1e/EMBEDDING used_tokens: 3

Expected behavior

No response

Steps to reproduce

1.select the model
2.upload files
3.click analyse
4.wait the log show error

Additional information

you can get the error log in:
https://aao615odquw.feishu.cn/sheets/TKNfs1QrEhD6jbtxdpFcXqvtn2d?sheet=1ppq8j

[dosubot]

@BadwomanCraZY Hello there! I'm here to assist you with any bugs, questions, and contributions. Let's work together to resolve this issue while we wait for a human maintainer.

I found some relevant information that might help address the issue you're experiencing with the LLMBundle.encode function failing to update token usage.

There is a similar unsolved discussion titled "Embedding model, do I need to set additional token? Why does my ragflow-server keep reporting errors in its ERROR.log?" which might provide some insights ^[1].

The common causes for the LLMBundle.encode function to fail in updating token usage are likely related to the TenantLLMService.increase_usage method. If this method returns False, it indicates a failure to update the token usage. Possible reasons for this failure could include:

1. Database or Service Unavailability: The service responsible for updating the token usage might be down or unreachable.
2. Invalid Tenant or Model Information: The tenant_id, llm_type, or other related identifiers might be incorrect or not properly registered in the system.
3. Exceeded Quota or Limits: The tenant might have exceeded their allowed token usage quota, preventing further updates.
4. Internal Errors: There could be internal errors within the increase_usage method that prevent it from executing successfully ^[2].

You might want to check these potential issues in your setup to see if they could be causing the problem.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[KevinHuSh]

You could ignore that error message.