Skip to content
Forums
Forums
How To
Troubleshooting Pos...
 
Notifications
Clear all

Troubleshooting Postgres Chat Memory and Supabase for AI Tools Agent

 
Page 1 / 2
How To
Last Post by zlebandit 7 months ago
20 Posts
13 Users
0 Reactions
8 Views
RSS
mxkel
 mxkel
(@mxkel)
Posts: 1
New Member
Topic starter
 

Describe the problem/error/question

I'm encountering an issue with a previously functional AI Agent that utilizes several tools, is connected to Supabase as a database, and employs Postgres Chat Memory, also linked to Supabase. When I attempt to run the agent now, I receive the following error:

“- Cannot use a pool after calling end on the pool
Cannot use a pool after calling end on the pool”

What is the error message (if any)?

“- Cannot use a pool after calling end on the pool
Cannot use a pool after calling end on the pool”

Error details

Other info

callin.io version

1.74.1 (Self Hosted)

Time

1/15/2025, 4:10:04 PM

Error cause

{}

Error in sub-node ‘Postgres Chat Memory‘

Cannot use a pool after calling end on the pool
Open node

Please share your workflow

Share the output returned by the last node

Information on your callin.io setup

  • callin.io version:1.74.1 (Self Hosted)
  • Database (Supabase):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (railway.app - self hosted):
  • Operating system: mac os
 
Posted : 15/01/2025 9:17 pm
n8n
 n8n
(@n8n)
Posts: 97
Trusted Member
 

It appears your topic is missing some crucial details. Could you please provide the following information, if relevant?

  • callin.io version:
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app):
  • Operating system:

Please provide the requested details.

 
Posted : 15/01/2025 9:17 pm
bluewerx
 bluewerx
(@bluewerx)
Posts: 4
New Member
 

I'm encountering the same problem after updating to version 1.74.1 today. The only distinction is that my instance is hosted on the cloud.

 
Posted : 16/01/2025 1:46 am
Danilo_Alves
 Danilo_Alves
(@danilo_alves)
Posts: 1
New Member
 

I'm encountering the same issue. After updating to 1.74.1 today, all my workflows that utilize postgres with AI agents are showing the same error.

  • callin.io version:1.74.1 (Self Hosted)
  • **Database (Postgres via Supabase):
  • **callin.io EXECUTIONS_PROCESS setting (default: main):
  • Running callin.io via (Hetzner - self hosted):
  • **Operating system: Ubuntu 20.04.6
 
Posted : 16/01/2025 4:50 am
MattB
 MattB
(@mattb)
Posts: 1
New Member
 

Experiencing the same problem on the cloud version.

 
Posted : 16/01/2025 5:27 am
samyfaisal
 samyfaisal
(@samyfaisal)
Posts: 1
New Member
 

I'm encountering the same problem following the recent update to version 1.74.1 (self-hosted on a cloud VPS).

 
Posted : 16/01/2025 6:49 am
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hi everyone, good news! We have a fix ready for this, which we hope to release this week.

Apologies for this, and thank you for your patience.

:pray:

 
Posted : 16/01/2025 8:56 am
Andres_Rafael
 Andres_Rafael
(@andres_rafael)
Posts: 4
New Member
 

Is it possible to revert to version 1.40.0 for the time being?

 
Posted : 16/01/2025 2:38 pm
Vicente_C
 Vicente_C
(@vicente_c)
Posts: 1
New Member
 

I'm encountering the same issue. After updating to 1.74.1 today, all my workflows that utilize PostgreSQL with AI agents are showing the same error.

  • callin.io version:1.74.1 (Self Hosted)
  • **Database (Postgres via Supabase):
 
Posted : 17/01/2025 8:58 am
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

Hello everyone, we've just released the fix in version 1.75.1.
If anyone could update and test again to see if the issue is resolved, we would greatly appreciate your feedback!

:slight_smile:

 
Posted : 17/01/2025 10:18 am
bluewerx
 bluewerx
(@bluewerx)
Posts: 4
New Member
 

I recently updated my cloud instance to version 1.75.1. I'm still encountering the same problem where a workflow query works correctly the first time, but then fails on the second attempt. The error message is “Cannot use a pool after calling end on the pool” when using the Postgres Chat Memory node.

 
Posted : 17/01/2025 12:09 pm
Diego_Alvarez
 Diego_Alvarez
(@diego_alvarez)
Posts: 2
New Member
 

Still not functioning for me. Version 1.75.1 (cloud)

 
Posted : 17/01/2025 12:29 pm
netroy
 netroy
(@netroy)
Posts: 5
Active Member
 

Are you encountering this problem with the standard postgres node too? Or is it exclusively with chat memory and AI tools?

Please share if you're experiencing this with the regular postgres node as well, or if it's only related to chat memory and AI tools.

 
Posted : 17/01/2025 12:51 pm
bluewerx
 bluewerx
(@bluewerx)
Posts: 4
New Member
 

In my workflow, I'm using only a Postgres Chat Memory node. When I restart and ask a question in my chat window, it executes and provides an answer as expected, with no errors.

However, if I open the Postgres Chat Memory node immediately afterward and click on the connection settings, I encounter this error even before attempting another question in the chat window: Couldn’t connect with these settings: Connection pool of the database object has been destroyed.

I've tested both port 5432 and 6543, and the outcome is the same.

If I wait a few minutes and then click the Retry button (to re-establish the connection), it indicates: Connection tested successfully.

At that point, I can successfully run the chat window with a question again, without any errors. This only fails if I try to ask a subsequent question immediately after. It's quite peculiar that it disconnects from the database after a successful query; it suggests a potential timeout issue.

Apologies for the lengthy explanation.

 
Posted : 17/01/2025 1:04 pm
Diego_Alvarez
 Diego_Alvarez
(@diego_alvarez)
Posts: 2
New Member
 

I'm currently using only the Postgres Chat Memory node.

 
Posted : 17/01/2025 1:12 pm
Page 1 / 2
Forum Jump:
  Previous Topic
Next Topic  
Share: