Unstable postgre connection

Questions
1

Describe the problem/error/question

Facing postgre connection instability.
Connection is fine at time, but it fails at other times.
No specific pattern: using the same postgre credentials in test or production (automation) mode could work or fail.

Has anyone faced this before, and if so, what took to fix it?
It is very annoying as I’m not able to reproduce on-demand due to its volatile nature.
This started to happen when I created a second postgre credentials to connect to another db.
So in total I have 2 db, with 2 n8n credentials (one each). The issue happens on the first (initially set) credentials only (for now)..

For the sake of it: I am able to access the db through n8n nodes (select, insert, query) properly in most of times, but at times, the workflow fails with the referred error message below.

Error message

Problem in node ‘xxxxx‘
database "xxxxx" does not exist

Workflow

In some cases, I’m using the postgre trigger to init a workflow, in other cases it is just using an insert to a db, or a select from the default postgre node.

Information on your n8n setup

  • n8n version: self-hosted 1.120.3
  • Database: postgre
  • Operating system: docker
3

I believe that the instability was due to the fact that I was using an Agent and I reached the max number of tokens through my various iteractions/testings. This issue is no longer the case since the model I use (Gemini) has increased their number of token and daily requests).

1 Like