Postgres trigger node not firing when workflow is published

[ralph_1982]

I’m running running n8n:2.3.6 as a self-hosted instance in a docker swarm network alongside with a supabase instance. The network between n8n and supabase is fine.
If’ve applied multiple postgres trigger nodes in one workflow. These trigger nodes listen for insert events on a specific table in a specific schema. All access to this schema is granted.
When triggering execute workflow on one of these trigger nodes, everything works as expected. When running in published mode, these triggers don’t execute anymore.
Is there any know issue with Postgres trigger nodes?

[Anshul_Namdev]

Hey @ralph_1982 Welcome to the n8n community!
This is expected behavior in n8n.

In published (active) mode, a workflow can only have one trigger node.
When you add multiple Postgres Trigger nodes to the same workflow, only one of them is actually registered when the workflow is activated. The others will silently not fire.

That’s why:

• Manual “Execute workflow” works

• Published mode does nothing

Fix:
Split each Postgres Trigger into its own workflow, or use one trigger and branch logic after it.

This limitation applies to all trigger nodes, not just Postgres. Let me know if this helps

[ralph_1982]

Dear @Anshul_Namdev,

thanks for the quick reply!
I will proceed with putting every trigger node to it’s own workflow.

Cheers!

[Anshul_Namdev]

Sure let me know if that works for you! And mark that as a solution if it helps you