n8n Workflow "Asleep"? Issue with PostgreSQL Trigger Not Firing

Hi everyone,

I’m experiencing what seems to be a bug with my n8n instance: some automations don’t always trigger as expected. For example, I have a workflow that’s triggered when a new row is inserted into a PostgreSQL database, but it doesn’t consistently run.

I did a manual test by inserting a new row, and this time the workflow triggered properly. Since then, it’s been working normally again — as if it had been “asleep” and needed to be woken up.But I can’t afford to have a workflow that only works if it’s been triggered recently or manually reactivated.

Has anyone encountered this kind of behavior before? If so, how did you solve it?

My n8n instance is hosted on my company’s servers, so I don’t have full access to the configuration settings.

2 comments