n8n - 💡(How to fix) Fix RabbitMQ trigger & Delete from queue options, not working as expected. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28605Fetched 2026-04-18 05:57:16
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

Bug Description

RabbitMQ trigger node behaves differently than stated.

When setting the 'delete from queue when' to 'Specifiek later in workflow': In production: message wil delete from the queue when workflow crashes. But it should be added back to the queue on crash ( would be nice ), else it should stay NACK, untill it reaches timeout, and then sent back to the queue.

In Editor mode: its hard to test, but it will stay NACK when crashed, and will stay NACK untill timeout reaches, and sends back to queue.

To Reproduce

In produciton(published).

  1. make a rabbitmq trigger, and set it to a queue.
  2. set it to the option, delete when delete message node is activated
  3. set timer of 20 seconds, then make it crash on purpose, without reaching the delete from queue node.
  4. Msg should be deleted from the queue, instead of moving back to the queue.

Expected behavior

I expect the message to be sent back to the queue on crashed workflow, and will retry on next trigger, untill it reaches the delete form queue node, then it should be deleted.

Debug Info

<img width="1547" height="617" alt="Image" src="https://github.com/user-attachments/assets/5f708f6f-0de6-4c8f-a5cf-eb6af1dbf5a8" /> <img width="1549" height="471" alt="Image" src="https://github.com/user-attachments/assets/9668e2fb-69e9-4286-b4a4-4ecdfd4aef43" />

These images were a production flow, where the flow purposely failed before reaching the node delete from queue, yet it shows the msg was still deleted from the queue.

Operating System

Windows 11

n8n Version

[email protected]

Node.js Version

unclear where to find it.

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

extent analysis

TL;DR

The RabbitMQ trigger node in n8n may be incorrectly deleting messages from the queue when the workflow crashes, instead of sending them back to the queue for retry.

Guidance

  • Verify the workflow configuration to ensure that the "delete from queue when" option is set to "Specific later in workflow" and that the delete message node is properly configured.
  • Check the RabbitMQ queue settings to confirm that the message acknowledgement and retry policies are correctly configured.
  • Test the workflow in a controlled environment to reproduce the issue and verify the expected behavior.
  • Consider increasing the timeout value to allow more time for the workflow to complete before sending the message back to the queue.

Example

No code snippet is provided as the issue is related to workflow configuration and RabbitMQ settings.

Notes

The issue may be specific to the n8n cloud hosting environment or the Windows 11 operating system. Further investigation is needed to determine the root cause of the problem.

Recommendation

Apply workaround: Modify the workflow to use a different acknowledgement strategy, such as manual acknowledgement, to ensure that messages are not deleted from the queue prematurely. This will allow for more control over message processing and retry logic.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

I expect the message to be sent back to the queue on crashed workflow, and will retry on next trigger, untill it reaches the delete form queue node, then it should be deleted.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

n8n - 💡(How to fix) Fix RabbitMQ trigger & Delete from queue options, not working as expected. [1 comments, 2 participants]