Hi, I want to ask why I don’t find any error marks located on the nodes in the workflow that I have. please see attachment.
usually if the workflow error it will be informed which node caused the error, but this is not.
why is this happening and how to fix it?
Hi @rusdiaman, I am very sorry you are having trouble.
Is there any additional information shown when opening these executions? Possibly a hint that n8n crashed when trying to execute the workflow in question? And can you manually execute the workflow?
Do you see any errors in your server logs around the time these executions took place?
Hi @MutedJam,
There is no additional information such as popups or anything else when I open the executable.
I’ve tried running manually and the result is success, no errors appear.
when I try to check the log it shows data like this
2023-07-11T02:53:03.657196942Z sorry, too many clients already
2023-07-11T02:53:03.848094083Z sorry, too many clients already
2023-07-11T03:03:06.443016502Z This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-07-11T03:03:06.443084634Z ResponseError: sorry, too many clients already
2023-07-11T03:03:06.443089130Z at Object.executeWebhook (/usr/local/lib/node_modules/n8n/dist/WebhookHelpers.js:431:15)
2023-07-11T03:03:06.443091477Z at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-07-11T03:03:06.809566305Z sorry, too many clients already
2023-07-11T03:03:07.046064000Z sorry, too many clients already
2023-07-11T03:08:06.907509371Z sorry, too many clients already
2023-07-11T03:08:06.928534791Z sorry, too many clients already
2023-07-11T03:17:54.198305545Z This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
2023-07-11T03:17:54.198353540Z ResponseError: sorry, too many clients already
2023-07-11T03:17:54.198357203Z at Object.executeWebhook (/usr/local/lib/node_modules/n8n/dist/WebhookHelpers.js:431:15)
2023-07-11T03:17:54.198363089Z at runMicrotasks ()
2023-07-11T03:17:54.198366143Z at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-07-11T03:17:55.729261143Z sorry, too many clients already
2023-07-11T03:17:55.744484757Z sorry, too many clients already
2023-07-11T03:17:56.707061760Z sorry, too many clients already
2023-07-11T03:17:56.735939261Z sorry, too many clients already
2023-07-11T03:17:57.049303413Z sorry, too many clients already
2023-07-11T03:28:09.872844437Z sorry, too many clients already
is this caused by too many webhook events coming in?
Oh, this looks like a Postgres error, so my best guess is that n8n is simply unable to load the execution details (or was previously unable to write these).
Is your database used by services other than n8n as well and perhaps simply busy? You can query the current connection limit using SHOW max_connections; and query the current usage by SELECTing from pg_stat_activity.
Hi @MutedJam ,
Database used only for n8n. when I check the maximum connection is 100 and when I check the current usage it’s only 15-21 connections.
Is there anything else I should check?
I am so sorry.
when I check the current usage it’s only 15-21 connections.
Are you still seeing “sorry, too many clients already” errors corresponding with your attempts to fetch execution data?
And are you getting any response when opening https://your.instance.url/rest/executions/145149 directly instead of opening the execution via the UI?
Hi @MutedJam
The error occurs at an unspecified time, sometimes every 10 minutes, sometimes once every 1 hour. so I can’t figure it out. and between those times, the workflow ran smoothly.
fyi, I just upgraded to the latest version, and found an error
“Workflow execution finished with an error Cannot read properties of undefined (reading ‘name’)”
at the time when i open the error executions.
i read in this community (ref : Javascript in node function ERROR: Cannot read properties of undefined (reading 'every') [Line 852] 4) and have tried it but still error.
Any other suggestions from you?
Hi @rusdiaman, to be honest I think we’re mixing up quite a few different issues here.
In order to help you it’d be great if you could share all details required to reproduce your problem. I too am using PostgreSQL on my private n8n instances, but don’t encounter the issue you are seeing despite using it 24/7 for various workflows. So any additional steps leading to your problem would be helpful. When running into the issue, are you possibly running a workflow interacting with the Postgres database?
Just based on the error message you have shared I suspect your database is under a high load at certain times and might require additional tuning as discussed here for example. That’s however not an n8n-specific problem and I can only offer limited advice on this part.
Your latest error and the thread you have linked suggests one of the nodes or code snippets in your workflow is simply trying to read something that’s not available, perhaps because it doesn’t account for all possible responses from an external API.
Perhaps you can share a simplified workflow (using mock data and not requiring any 3rd party credentials I might not have) using which your problem can be reproduced?
Hi @MutedJam
Sorry, I thought it was the same problem.
Below is one of the workflows that experience this.
I have also tried following the link you provided. but the result is still the same.
Still hoping I can find a solution of this problem.
Thanks for your time, @MutedJam
Hm, this workflow doesn’t look particularly problematic to me.
Can you try opening https://your.instance.url/rest/executions/145149 as suggested earlier directly and confirm if you’re seeing any execution data returned by the endpoint?
