Hello,
I’m using Flowise as a no code builder to create conversational chatbots. I’ve been using Pinecone for my vector store and Supabase as my record manager.
I used Flowise to build my chatbot flow that upserted new Airtable entries as vectors into a Pinecone index each time I manually ran the Upsert function on Flowise.
This was all working perfectly fine but it required manual upserting, so I setup an automation in Make.com which would call the URL to trigger the API and upsert on a periodic basis at a cadence of my choosing (I picked every 4 hours).
This worked fine for a short while before the automation stopped and now I’m unable to even upsert manually from Flowise.
Here is the following error I get whenever I try to upsert new data:
‘Error: vectorsService.upsertVector - Error: error: Max client connections reached’
It seems that API has opened connections but not closed them, which conflicts with Pinecones 10 connection limit.
Anyone know how to get around this? Or how to reset the connections so I can just go back to manual for now? Not being able to update the vectors is a serious blocker so would reallt appreciate any help to get around it. I’m a no code noob so been reliant on Flowise to build it visually which was working but now fear I’ve broken it 
Many thanks in advance!
Hi @ben.mushen, and welcome to the Pinecone community forums!
Thanks for your question.
It’s unfortunately pretty difficult to discern what might be going wrong given that both platforms are low/no-code.
Do either have the option of turning on more verbose logging? Have you tried posing the same question to Flowise/Make?
Best,
Zack
Hi @ZacharyProser, thanks for getting back to me!
Not on the plan of Make I’m on and I can’t seem to find a way to get more details out of Flowise sadly. Flowise doesn’t seem to have much support outside of having an enterprise plan but I’ve just setup my own instance of the open source framework. Make has support, which I fear that’s what’s caused the issue but I’ve since deleted the automations in Make and I don’t think that’s where the issue lies now.
It definitely seems to be an issue with my Pinecone connections maxing out but I’ve no idea how to reset them sadly
Any ideas on how I could factory reset this without having to delete the index would be super helpful! The store is quite a size now and it could be a chore to have to re-upsert everything, now quite sure how to batch through Flowise either
Many thanks for your comment!
Ben
Hi Ben,
Understood - one hopefully helpful suggestion I can offer is to look into collections as a means of “saving” or freezing a copy of your index, since you mention its current state is important to you and you don’t want to lose it.
At a high-level, since everything in engineering is a trade-off, this is one of the key trade-offs with low/no-code tools - they can be faster and easier to use when you’re treading the happy path, but as soon as you want or need more control or observability, you’re at a significant disadvantage, stuck with whatever that tool makes available.
For what it’s worth, we do have a ton of notebook examples in github.com/pinecone-io/examples - There’s a video plus screenshot-heavy guide there that walks you through how to load them in Google Colab and run them (and now with Colab’s GenAI features, you could get help modifying them) - those would be a great lightweight way to dip a toe into a version of your app you have more control over.
Let me know if that helps!
Best,
Zack
Hi Zack,
Thanks for the feedback, I’ll definitely look more into collections thanks.
Thankfully, I managed to resolve it for now. I deleted some old instances and just left it for a while, then when I later tried again it worked! Time truly can be a healer I suppose! Not sure what the issue was but yeah I can definitely see the trade offs now haha!
Thanks for the resources, I’ll check them out when I get a chance.
Many thanks for your help again!
Ben