Unable to automatically perform embedding processing after uploading documents using the API?

[gongshaojie12]

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I can upload files normally using the create-by-file method, but I cannot automatically perform the embedding process. I can only manually click "Save and Process" in the "Segmentation Settings" of the Dify interface to perform the embedding process. How can I set it to automatically perform the embedding process after uploading?

✔️ Expected Behavior

It is hoped that after uploading documents using the API, the embedding process can be automatically performed.

❌ Actual Behavior

No response

[dosubot[bot]]

The issue you're experiencing with the automatic embedding process not triggering after document upload via the API might be related to configuration settings or flags that control this behavior. Unfortunately, I couldn't find specific information in the repository about a configuration or flag that enables automatic embedding after document upload.

However, the embedding process is typically managed by the EmbeddingProcess component, which uses the startQueryStatus function to check the indexing status and proceed with embedding ^[1]. You might want to ensure that this component is correctly set up and that there are no interruptions in its execution.

If the automatic process is not working as expected, you may need to manually trigger the embedding process as a temporary workaround. Additionally, reviewing the server logs for any errors or warnings during the upload and embedding process might provide more insights into the issue.

If you have access to the codebase, you could also check if there are any conditions or prerequisites that need to be met for the embedding process to trigger automatically. This might involve looking into the API's handling of document processing and embedding transitions ^[2].

To continue talking to Dosu, mention @dosu.

---

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