Pinecone GetMany Function not returning anything

Questions
1

Describe the problem/error/question

My Pinecone node is not finding any results when using the “Get Many” Operation mode.

I first upload my files with another Pinecone Node and a Token Splitter, with the samme openAI embeddings “text-embedding-3-small”.

When checking this in pinecone, I can see that the document was uploaded correctly in the format I want to have.

However, when trying the most basic query (I also tried including meta data filters or removing the namespace), I simply get no result at all.

I double checked that I am using the correct Pinecone Index, however, there simply is no output at all.

Also, even when switching the “Always Output Data” Option on, it still doesnt work.

Am I missing something crucial here? there are no more options to add within the request, so I am really unsure on what to tackle next.

Thank you for any help in advance!

What is the error message (if any)?

There is no error message. The node is simply not returning anything, even if I switch on the “Always Output Data” Option.

Please share your workflow

Share the output returned by the last node

There simply is no output at all.

Information on your n8n setup

  • n8n version: 1.91.3
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: Windows
2

Since noone else answered yet, I will contribute some additional findings I noticed:

  • When just having a basic “Test Workflow” Trigger Node in front of my pinecone node (1:1 similar code), everything works as expected.
  • However, when I have a Classifier Node in front of it, suddenly there is no more result. I also tried adding different “placeholder” nodes between the classifier and the pinecone node (like e.g. a “Wait” or a “Set” Node), which worked once (!), but stopped working afterwards immediately again.
  • I tried reproducing it, but I cannot identify any clear structure on when it works, and when it doesnt, with the exception that it almost never seems to work after a classifier node

This leads me to the conclusion, that this must be some kind of n8n bug.
Having the exact same Node in two different places, without any input from the previous node, and once it works, once it does not, seems like there must be something under the hood that is responsible for that.

Not sure how I can tag this as a bug, would be nice if someone could help me out,

3

Heya! Had the same problem as you - managed to resolve it by updating my n8n version to the latest one. Give it a try and see if it works :slight_smile:

1 Like
4

Thank you, will give it a shot!