You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to upsert a document via the Unstructured File Loader via the Flowise API, the file attached in the POST call is ignored, and the file specified in the node in the UI is uploaded instead. This was previously fixed for the PDF loader (thank you!), but is still present for Unstructured File Loader.
In this call, a PDF of a short story (several pages long) is attached. As you can see in the response, the file that was upserted was the file "blank.pdf", which is a single page with the words "ERROR" on it that was uploaded directly into the Unstructured File Loader node:
Expected Behavior
The attached file (above: Girl Jamaica Kincaid.pdf) should replace the file in the node (above: blank.pdf) and be upserted.
Flow & Config
Below is an example flow and override configuration to recreate this behavior:
Setup
Installation: RepoCloud instance
Flowise v2.2.2
The text was updated successfully, but these errors were encountered:
Describe the bug
When trying to upsert a document via the Unstructured File Loader via the Flowise API, the file attached in the POST call is ignored, and the file specified in the node in the UI is uploaded instead. This was previously fixed for the PDF loader (thank you!), but is still present for Unstructured File Loader.
In this call, a PDF of a short story (several pages long) is attached. As you can see in the response, the file that was upserted was the file "blank.pdf", which is a single page with the words "ERROR" on it that was uploaded directly into the Unstructured File Loader node:
Expected Behavior
The attached file (above: Girl Jamaica Kincaid.pdf) should replace the file in the node (above: blank.pdf) and be upserted.
Flow & Config
Below is an example flow and override configuration to recreate this behavior:
Setup
The text was updated successfully, but these errors were encountered: