Based on the search results, this appears to be a known issue with Supabase Vector Store nodes returning empty arrays. Here are the key troubleshooting steps:
• **Check your Supabase function setup** - Ensure the `match_documents` function is properly created in your database. According to [community.n8n.io]( Error with Supabase Vector Stores ), you need to run the complete SQL setup script that creates both the table and the search function.
• **Verify embedding dimensions match** - The [github.com]( Error searching for documents: 22000 different vector dimensions 768 and 192 null · Issue #16517 · n8n-io/n8n · GitHub ) issue shows dimension mismatches can cause problems. Since you’re using text-embedding-3-small (1536 dimensions), make sure your Supabase table’s vector column is also set to 1536, not a different dimension.
• **Test with a simple query first** - Try using the Supabase Vector Store in “Insert Documents” mode first to confirm the connection works, then switch back to “Retrieve Documents” mode. This helps isolate whether it’s a connection or retrieval-specific issue.
• **Check table/column naming** - Table names with spaces (like “Sollex Products”) can sometimes cause issues. Try creating a test table with a simple name (no spaces, lowercase) to see if that resolves the problem.