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
While working with the Qdrant Vector Store node in n8n, some of the files I am trying to store are larger than the embedding model's context length. This causes an error in the Ollama Embeddings sub node. However, the parent node (Qdrant Vector Store node) only appears errored in the UI but behaves as if it succeeded and returns its input as it is. This issue is evident when I attempt to catch the error using the "Continue using error output" setting in the node's settings. After failing, the node returns its input in the "success" output, as shown in the attached photos.
This looks similar to this past issue: #8921
To Reproduce
1.Use the Qdrant Vector Store node in a workflow.
2.Attempt to store files larger than the embedding model's context length.
3.Observe the error in the Ollama Embeddings sub node.
4.Notice that the Qdrant Vector Store node appears errored in the UI but behaves as if it succeeded.
5.Enable "Continue using error output" in the node's settings.
6.Observe that the node returns its input in the "success" output after failing.
Expected behavior
The Qdrant Vector Store node should properly indicate an error and retrun the error message in the error output and not return its input as if it succeeded.
Operating System
Alpine Linux v3.21 (self hosted)
n8n Version
1.80.3
Node.js Version
v20.18.2
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered:
Bug Description
While working with the Qdrant Vector Store node in n8n, some of the files I am trying to store are larger than the embedding model's context length. This causes an error in the Ollama Embeddings sub node. However, the parent node (Qdrant Vector Store node) only appears errored in the UI but behaves as if it succeeded and returns its input as it is. This issue is evident when I attempt to catch the error using the "Continue using error output" setting in the node's settings. After failing, the node returns its input in the "success" output, as shown in the attached photos.
This looks similar to this past issue: #8921
To Reproduce
1.Use the Qdrant Vector Store node in a workflow.
2.Attempt to store files larger than the embedding model's context length.
3.Observe the error in the Ollama Embeddings sub node.
4.Notice that the Qdrant Vector Store node appears errored in the UI but behaves as if it succeeded.
5.Enable "Continue using error output" in the node's settings.
6.Observe that the node returns its input in the "success" output after failing.
Expected behavior
The Qdrant Vector Store node should properly indicate an error and retrun the error message in the error output and not return its input as if it succeeded.
Operating System
Alpine Linux v3.21 (self hosted)
n8n Version
1.80.3
Node.js Version
v20.18.2
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: