Rabbitmq arguments not set as expected

Questions
,
1

Describe the problem/error/question

The queue arguments that are set through the RabbitMQ trigger node configuration are not set in the RabbitMQ server as expected. Is this a bug?

What’s set in n8n rabbitmq node trigger:

image
image562×1567 50.8 KB

Observation:

image
image1863×847 103 KB

What is the error message (if any)?

RabbitMQ queue arguments are not set as expected.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.115.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): self hosted on k8s
  • Operating system:
2

Based on the search results and your configuration, this appears to be a known issue with RabbitMQ queue arguments not being properly set through the n8n trigger node. The problem is similar to [Issue #2806]([RabbitMQ node] arguments are not added to the message · Issue #2806 · n8n-io/n8n · GitHub) where arguments aren’t correctly passed to the RabbitMQ server.

Here are some practical solutions to try:

• **Check argument format**: Ensure your queue arguments are properly formatted as key-value pairs in the node configuration

• **Use RabbitMQ management interface**: Create the queue with the correct arguments directly in RabbitMQ first, then connect n8n to the existing queue

• **Alternative approach**: Consider using the regular RabbitMQ node (not trigger) to declare the queue with proper arguments before setting up the trigger

• **Verify n8n version**: This might be resolved in newer versions - check if updating n8n helps

If the issue persists, you may need to pre-configure your queues with the desired arguments directly in RabbitMQ management console before connecting your n8n workflow.