-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(RabbitMQ Trigger Node): Automatically reconnect on disconnect #4019
Conversation
// eslint-disable-next-line @typescript-eslint/no-unsafe-argument | ||
this.executeErrorWorkflow(error, workflowData, 'internal'); | ||
|
||
// Keep on trying to activate the workflow | ||
this.addQueuedWorkflowActivation('init', workflowData); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to check for the error type here? as in, retry only if it's a network issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested by shutting down my rabbitmq container. The workflow successfully reactivated on startup, as well as on a connection retry.
Got released with |
…8n-io#4019) * feat(RabbitMQ Trigger Node): Automatically reconnect on disconnect * ⚡ Retry indefinetly * ⚡ Also automatically retry activation issues on startup
To fix issue #1988
https://community.n8n.io/t/no-reconnect-if-rabbitmq-server-restarts/5572