-
-
Notifications
You must be signed in to change notification settings - Fork 24.1k
File Loader Not Picking Up Provided File(s) from Request - After Upgrading from 3.0.4 to 3.1.1 #6102
Description
Describe the bug
I have a very basic ingestion flow.
In version 3.0.4 this worked, and I was able to upsert to pinecone successfully. However, I couldn't use anthropic's new chat models due to a different bug, so we decided to upgrade our instance to 3.1.1. After upgrading, this ingestion flow no longer indexes anything.
Over the course of trying to debug this, I tried manually providing a file in the File Loader node, and hitting the Upsert button directly within Flowise. This also indexed nothing, and showed all zeros. I then replaced each node one at a time to no avail, but after setting it back to the original flow, this same manual scenario now worked. I think deleting and re-adding the connections between nodes somehow got me past some problem. Anyways, I then went to upload a different file from my web app hooked up to this flow, with a File still specified in the File Loader node, and I was successful. However, it just upserted that static file over and over again, not the one I was providing in the request. I removed the defined file from the File Loader node, and I am back to square one where the call is successful but nothing is indexed/added.
To Reproduce
- Be on version 3.1.1 and create an ingestion flow similar to mine.
- I have the File and Additional Metadata set to overridable in the override config.
- Make a multi-part form data request with a File provided. (I am using RestSharp in .NET)
var request = new RestRequest($"/api/v1/vector/upsert/{chatflowId}", Method.Post);
request.AddFile("files", fileBytes, fileName, mimeType);
- Nothing gets indexed.
Expected behavior
I would expect the file uploaded to ingest the file provided in the request, and index and chunk it, and send that to pinecone, as it did before.
Screenshots
No response
Flow
Use Method
Docker
Flowise Version
3.1.1
Operating System
Linux
Browser
None
Additional context
Without any changes whatsoever, this was working in version 3.0.4. It is no longer working after upgrading to 3.1.1.