RabbitMQ trigger not producing any output when workflow is activated

Questions
1

Describe the problem/error/question

I have a workflow including RabbitMQ trigger. The credentials are well verified. Everything is working well when I test manually my unactivated workflow.
The problem appears when I activate my workflow : The Rabbit MQ trigger is executed but it produces no output.

What is the error message (if any)?

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.7.1
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker container in kubernetes cluster
  • Operating system: Linux
2

Hi @alt-f12

Welcome to the community!

Do other triggers work? Seems like there are no workers running here.

3

Hi !
I’ve just tested the Scheduled trigger… working well.
For RabbitMQ Trigger, I can see executions launched each time a message is posted to RabbitMQ but no the triggers doesn’t output the consumed message

4

Really weird now !
I publish a message to RabbitMQ, the n8n triggers is executed and I have the following error

ERROR: Node has no access to credential
Please recreate the credential or ask its owner to share it with you.

Don’t understand because my credential has just been created before editing the workflow, and it is verified, and everything is working well when testing my workflow using Listen for event button

5

Hey @alt-f12,

Can you try updating n8n, It may also be handy if you can share if your n8n configuration.

6

I’m using the Helm chart n8n 0.13.0 · 8gears/open-8gears to deploy n8n via argoCD on my Kubernetes cluster.
I’ll try to build my own Helm chart

7

Hey @alt-f12,

I have seen a few differnet issues reported from people using that but it is not one we have tested so I do wonder if maybe there is an issue in there.

I would also recommend upgrading as that can often help fix issues as we do releases weekly, Maybe instead of running in a k8s cluster it might be worth starting with just one instance of n8n running in Docker to confirm it works then start splitting it up.

8

Thanks, first of all I will upgrade the n8n image used in the helm chart… let’s see !

9

I’ve just upgraded the n8n image used in my helm chart.
Always the same problem : testing the unactivated trigger works very well.
When it’s activated, I have an error :

Here is the error in n8n screen

ERROR: Node has no access to credential
Please recreate the credential or ask its owner to share it with you.

And here is the error in the pod logs :

NodeOperationError: Node has no access to credential
Error: Node has no access to credential
WorkflowOperationError: There is no active execution with id "524".
There was a problem running internal hook "onWorkflowPostExecute" WorkflowOperationError: There is no active execution with id "524".
at ActiveExecutions.getPostExecutePromise (/usr/local/lib/node_modules/n8n/dist/ActiveExecutions.js:122:19)
at WorkflowRunner.run (/usr/local/lib/node_modules/n8n/dist/WorkflowRunner.js:133:62)
at processTicksAndRejections (node:internal/process/task_queues:95:5) {
level: 'error',
tags: undefined,
extra: undefined,
context: {},
severity: 'warning',
functionality: 'regular',
timestamp: 1702037531729,
node: undefined
}
10

:thinking: That is unusual, Can you try remaking the workflow and the credential?

11

OK, I deleted and re-created my credentials and my workflows and everything is OK now.
I’m quite perplex ! :exploding_head:

1 Like
12

Hey @alt-f12,

My thinking on that one was maybe the workers were not correctly reading the database and it was causing some odd issue.

13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.