NATS JetStream trigger stops working after backend restart

[vlad-hi]

Description:
I’ve encountered an issue when using the NATS JetStream trigger in n8n.
• I have a backend running with an in-process NATS server.
• When an n8n workflow is configured with a NATS trigger, everything works fine initially.
• However, if the backend is restarted, the workflow’s NATS trigger seems to stop listening.
• To make it work again, I have to disable and re-enable the workflow manually.

Expected behavior:
The NATS trigger should automatically reconnect and continue working after the backend restarts.

Actual behavior:
After a backend restart, the trigger silently stops receiving messages until the workflow is toggled off/on again.

Steps to reproduce:
1. Run a backend with in-process NATS.
2. Connect n8n to it and create a workflow with a NATS trigger.
3. Restart the backend.
4. Notice that the workflow no longer reacts until it’s manually restarted.

Environment:
• n8n version: 1.109.1
• NATS JetStream plugin version: 0.3.2

Possible cause:
It looks like the NATS trigger doesn’t handle reconnections after the server goes down and comes back up.