[BUG] Provided file is ignored when upserting via API

[kennyakers]

Describe the bug
When POSTing a file to the /vector/upsert/{id} endpoint, the provided file is ignored, and instead the file uploaded within the Flowise UI is upserted. In my case, I'm upserting PDFs to a Pinecone vector store. All credentials have been double-checked.

To Reproduce

An example upsertion flow is shown below:

Override config has been enabled so API calls should be able to overwrite the PDF file:

Note that the file originally uploaded is of the classic book Frankenstein. When I make a call to upsert a different book, Of Mice and Men, Frankenstein still ends up getting upserted (see response):

If I remove the file from the "PDF Loader" node, uploading any PDF (I even used the same Frankenstein file) to it will result in 0 documents getting upserted:

Expected behavior
The file provided in the form data should be upserted, not the file originally uploaded.

Setup

• Installation: Repocloud.io instance
• Flowise Version 2.1.5

Additional context
This only started becoming a problem ~3-4 weeks ago (i.e., beginning of November). It was working for months before then.

[ThijsObers]

I face the same issue as well. When I move back to version 2.1.3, it still works. (I have not tried 2.1.4 yet)

[HenryHengZJ]

thanks for reporting, I knew something was missing! Fix is here: #3569, will be pushed to new release some time this week

[marsalan06]

any update on this issue ? the version 2.2.1 still has this bug :/

[kennyakers]

any update on this issue ? the version 2.2.1 still has this bug :/

It appeared to be fixed briefly after upgrading to v2.2.1, but returned to the original behavior soon after.

After trying both the PDF loader and Unstructured loader (same result), the upsert history shows the 'files' parameter is never updated with the API-provided file -- perhaps the override config isn't taking effect here?

@HenryHengZJ hope that ^ context is useful. Appreciate all your work.