You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently have an AMQP Trigger that is subscribed to our system Azure Service Bus queue for n8n to pick up events to process.
We recently encountered a number of other issues with AMQP nodes but this is the most critical:
For no apparent reason the trigger will stop to process events. (ie n8n or database or service bus services are not interrupted according to logs and there are no errors being logged)
This is critical since it stops critical event-based workflows to be executed.
When the workflow is de-activated and re-activated the events (thousands of them) get processed again immediately.
This might not be version dependent but the first time this was observed was on 1.78+
What is the error message (if any)?
None - checked all logs available including log stream and console / system logs.
Describe the problem/error/question
We currently have an AMQP Trigger that is subscribed to our system Azure Service Bus queue for n8n to pick up events to process.
We recently encountered a number of other issues with AMQP nodes but this is the most critical:
For no apparent reason the trigger will stop to process events. (ie n8n or database or service bus services are not interrupted according to logs and there are no errors being logged)
This is critical since it stops critical event-based workflows to be executed.
When the workflow is de-activated and re-activated the events (thousands of them) get processed again immediately.
This might not be version dependent but the first time this was observed was on 1.78+
What is the error message (if any)?
None - checked all logs available including log stream and console / system logs.
Please share your workflow/screenshots/recording
Debug info
core
storage
pruning
client
Generated at: 2025-02-23T22:30:09.150Z}
The text was updated successfully, but these errors were encountered: