dify - 💡(How to fix) Fix document queuing [3 comments, 3 participants]

TL;DR

Check the vector model's request rate limiting configuration to ensure it properly resets after the rate limit is canceled.

Guidance

• Review the Dify version 1.13.3 documentation to understand how the vector model's request rate limiting works and how it handles queued documents after the rate limit is canceled.
• Investigate the vector knowledge base configuration to see if there are any settings that could be causing the queued documents to still indicate that the model request rate has been exceeded.
• Verify that the cancelation of the model request rate is properly propagated to the queue processing mechanism to ensure that queued documents are vectorized again.
• Check the Docker container logs for any errors or warnings related to the vector model or queue processing that could indicate the root cause of the issue.

Example

No code snippet is provided as the issue does not contain enough technical details to create a specific example.

Notes

The issue may be related to a configuration or implementation detail specific to Dify version 1.13.3 or the self-hosted Docker setup. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check and adjust the vector model's request rate limiting configuration to ensure proper handling of queued documents after the rate limit is canceled, as the root cause is likely related to this configuration.