[Bug]: No doc_status created after process_document_complete

[Yukari-Tryhard]

Do you need to file an issue?

• I have searched the existing issues and this bug is not already filed.
• I believe this is a legitimate bug, not just a question or feature request.

Describe the bug

No kv_store_doc_status is generated after unning process_document_complete.

I believe there is something related to the multimodal_content varible when calling ainsert in your source code. Apparently there is no multimodal_content in the latest branch of lightrag and it leads to a silent failure.

And our ultimate goal is to run adelete_by_doc_id to delete a document. but right now it just returned 404 not found due to no doc_status found

Steps to reproduce

So i run process_document_complete with these parameters:

await rag.process_document_complete(
            file_path=uploaded_file_path,
            output_dir="output",
            parse_method="auto",
            backend="pipeline",
            doc_id=custom_doc_id,
            file_name=data_item.filename,
        )

but the doc_status file is not generated as in the image below:

Expected Behavior

The doc_status should be created

LightRAG Config Used

Paste your config here

Logs and screenshots

RAGAnything ainsert screenshot:

lightrag ainsert screenshot:

Additional Information

• LightRAG Version:1.4.14
• Operating System:Windows 10 Pro 22H2 OS build: 19045.6466
• Python Version: Python 3.10.10
• Related Issues:

[Yukari-Tryhard]

@LarFii can you have a look at this