Rabbit MQ triggers do not work in test mode #8871

DRIMOL · 2024-03-12T23:40:49Z

Bug Description

A - Does not pull the item from the queue in test mode

B - If you write a message to a queue that does not exist, it returns an error.
ERROR: Operation failed: QueueDeclare; 404 (NOT-FOUND) with message "NOT_FOUND - no queue 'test_queue' in vhost 'default'

To Reproduce

A1 - adicione uma nova mensagem no rabbit mq
A2 - coloque o triggers em modo de escuta

A PS: No painel do rabbit MQ a messagem entra em Unacked, mas, no workflow do n8n nada acontece

B1 - try to write a message to a queue that doesn't exist

Expected behavior

A - Test message reception by rabbit MQ

B - Create new queues through the RabbitMQ node

Operating System

UbuntoLinux 20

n8n Version

1.31.2

Node.js Version

v18.19.1

Database

PostgreSQL

Execution mode

queue

Joffcom · 2024-03-13T11:20:13Z

Hey @DRIMOL,

Thanks for reporting this, I have created NODE-1230 as the ticket to fix the bug, With the second one I would expect it to fail if the queue doesn't exist as we don't set the option to create it.

If you want us to add this I would recommend creating a feature request on the community support forum and we can track the popularity of this and look at adding it in the future.

DRIMOL · 2024-03-13T13:45:28Z

I thought it was a BUG, because in version 1.24.1 it creates the queue if it doesn't exist.

Thanks

Joffcom · 2024-03-13T16:24:52Z

Hey @DRIMOL,

That was some important information that was missing... Looking at the release this was changed in 1.28.0 with this PR: #8430 and it looks like I missed that the change was not added to the standard node.

I will get that fixed shortly for the next release.

DRIMOL · 2024-03-20T19:30:41Z

Where can I track the progress?

Joffcom · 2024-03-21T10:53:12Z

Hey @DRIMOL,

This is the best place to check, Once fixed we will put a note on here to let you know. You can also keep an eye on the PR list to see if any of them contain node-1230.

Right now this is sat with a high priority and is waiting to be picked up.

barn4k · 2024-04-11T21:47:09Z

Actually, better to have an option like "Create if no queue" to avoid misconfigurations.

But I can imagine only one scenario when it might be needed - If someone by mistake has deleted a queue

barn4k · 2024-05-10T13:15:42Z

Hey @Joffcom , bug with the 404 instead of creating a queue is still there...

Joffcom · 2024-05-13T14:02:15Z

I have created a PR to fix the queue creation, Oddly enough when testing I noticed that running in test mode is working as well. @DRIMOL / @barn4k are you able to check on 1.41.0 to see if the test execution is working for an existing queue?

Joffcom · 2024-05-13T14:16:29Z

Thanks to a quick review from @netroy it looks like the option to make the queue is there already under Add Option > Assert Queue. This should resolve the issue of the queue not being created automatically.

barn4k · 2024-05-15T09:30:19Z

I have created a PR to fix the queue creation, Oddly enough when testing I noticed that running in test mode is working as well. @DRIMOL / @barn4k are you able to check on 1.41.0 to see if the test execution is working for an existing queue?

Well, I can't check it right now as the latest docker version is 1.39.1 :)

Joffcom · 2024-05-15T15:38:20Z

@barn4k latest should be 1.41.0 now 😄

barn4k · 2024-05-16T14:15:33Z

@Joffcom
Just tested on 1.41.1, Test Workflow/Test Step still don't work. It keeps loading forever

And I see that the node tried to consume the message but it stucked there (Unacked state)

Even after I have stopped the execution, it still holds the message

I've tried both: using the current RabbitMQ node and creating a totally new one

DRIMOL · 2024-05-16T18:43:01Z

I have created a PR to fix the queue creation, Oddly enough when testing I noticed that running in test mode is working as well. @DRIMOL / @barn4k are you able to check on 1.41.0 to see if the test execution is working for an existing queue?

Well, I can't check it right now as the latest docker version is 1.39.1 :)

here it is also loading infinite

na versão 1.41.0

DRIMOL · 2024-05-16T18:46:01Z

Thanks to a quick review from @netroy it looks like the option to make the queue is there already under Add Option > Assert Queue. This should resolve the issue of the queue not being created automatically.

yes, it already exists in the trigger, but the interesting thing would be if it was in the "Send a Message to RabbitMQ", because then we would be able to create queues dynamically.

DRIMOL · 2024-06-06T18:20:34Z

Será que ainda vão resolver ? 😞

luizeof · 2024-06-06T22:59:07Z

@Joffcom Setting Up N8N_LOG_LEVEL=verbose I can see the error that happens when the rabbit trigger is started:

2024-06-06T22:56:04.076Z | error    | There was a problem with the RabbitMQ Trigger node "RabbitMQ Trigger" in workflow "hAKRgkvpANXAoSTW": "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function" "{\n  node: 'RabbitMQ Trigger',\n  workflowId: 'hAKRgkvpANXAoSTW',\n  file: 'LoggerProxy.js',\n  function: 'exports.error'\n}"

ramonmatosweb · 2024-06-06T23:29:36Z

n8n20ylvns_n8n20ylvns_logs.txt

Joffcom · 2024-06-27T15:39:12Z

This will be fixed very soon.

DRIMOL · 2024-07-01T13:39:38Z

This will be fixed very soon.

I would like to add a bug that I noticed these days also about the rabbit

If I inactivate or delete an n8n flow where there is a rabbit trigger, the consumer is not automatically deleted from the rabbit, and continues to be sent to a ghost consumer, even though it has been deleted, the problem is only solved by updating n8n with prune , by doing this he excludes ghost consumers.

netroy · 2024-07-01T14:24:16Z

If I inactivate or delete an n8n flow where there is a rabbit trigger, the consumer is not automatically deleted

When you deactivate the workflow, do you see any error in the container logs saying something like There was a problem closing the RabbitMQ Trigger node connection?

DRIMOL · 2024-07-01T14:32:56Z

If I inactivate or delete an n8n flow where there is a rabbit trigger, the consumer is not automatically deleted

When you deactivate the workflow, do you see any error in the container logs saying something like There was a problem closing the RabbitMQ Trigger node connection?

I will try to check if I should look at this log in the n8n workers or in the RabbitMQ container?

netroy · 2024-07-01T15:03:06Z

I will try to check if I should look at this log in the n8n workers or in the RabbitMQ container?

Please check in the n8n worker logs.

DRIMOL · 2024-07-01T20:58:01Z

I tried to catch the bug here, but it excluded the consumer, it could have happened because the queue had a stuck message, for example when "parse json" is marked and the message arrives outside of the json format, in this case or something similar does not exclude, but by deleting a trigger that is "healthy" here the consumers were excluded from the rabbit

ianpogi5 · 2024-07-08T10:18:52Z

@Joffcom Setting Up N8N_LOG_LEVEL=verbose I can see the error that happens when the rabbit trigger is started:

2024-06-06T22:56:04.076Z | error    | There was a problem with the RabbitMQ Trigger node "RabbitMQ Trigger" in workflow "hAKRgkvpANXAoSTW": "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function" "{\n  node: 'RabbitMQ Trigger',\n  workflowId: 'hAKRgkvpANXAoSTW',\n  file: 'LoggerProxy.js',\n  function: 'exports.error'\n}"

Same error as mine

netroy · 2024-07-08T10:23:36Z

"Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function"

This error makes me wonder if the node_modules package is somehow tampered.

@ianpogi5 Are you running n8n on docker? and do you have any custom or community nodes installed?

ianpogi5 · 2024-07-08T11:30:25Z

"Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function"

This error makes me wonder if the node_modules package is somehow tampered.

@ianpogi5 Are you running n8n on docker? and do you have any custom or community nodes installed?

We are using docker version.

netroy · 2024-07-08T11:33:14Z

We are using docker version.

and do you have any custom or community nodes installed?

netroy · 2024-07-08T22:04:22Z

I need a way to reproduce this, to be able to fix this. Are you able to reproduce this on a new n8n instance, with a minimal workflow?

ianpogi5 · 2024-07-08T22:09:21Z

I need a way to reproduce this, to be able to fix this. Are you able to reproduce this on a new n8n instance, with a minimal workflow?

Here's my workflow:

{
  "name": "RabbitMQ test",
  "nodes": [
    {
      "parameters": {},
      "id": "f8f644e7-754e-44e1-a013-01dc0b309d8e",
      "name": "When clicking ‘Test workflow’",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        440,
        500
      ]
    },
    {
      "parameters": {
        "assignments": {
          "assignments": [
            {
              "id": "4c738ba4-d63b-4196-9297-e71e1f45ebca",
              "name": "name",
              "value": "Hello world!",
              "type": "string"
            }
          ]
        },
        "options": {}
      },
      "id": "d8530558-9790-4966-b529-0ae36ed22966",
      "name": "Edit Fields",
      "type": "n8n-nodes-base.set",
      "typeVersion": 3.4,
      "position": [
        680,
        500
      ]
    },
    {
      "parameters": {
        "queue": "n8n-test",
        "options": {}
      },
      "id": "cce5f6c4-bb8a-4307-86a5-9c454a7b1349",
      "name": "RabbitMQ",
      "type": "n8n-nodes-base.rabbitmq",
      "typeVersion": 1.1,
      "position": [
        940,
        500
      ],
      "credentials": {
        "rabbitmq": {
          "id": "poc4UQ08c1GLjORk",
          "name": "RabbitMQ account"
        }
      }
    },
    {
      "parameters": {
        "queue": "n8n-test",
        "options": {}
      },
      "id": "09021137-6b9f-48d7-b500-8989f2247359",
      "name": "RabbitMQ Trigger",
      "type": "n8n-nodes-base.rabbitmqTrigger",
      "typeVersion": 1,
      "position": [
        600,
        820
      ],
      "credentials": {
        "rabbitmq": {
          "id": "poc4UQ08c1GLjORk",
          "name": "RabbitMQ account"
        }
      }
    },
    {
      "parameters": {
        "operation": "deleteMessage"
      },
      "id": "09bf2dc7-8c18-4eae-941e-c7c6ed60c94a",
      "name": "RabbitMQ1",
      "type": "n8n-nodes-base.rabbitmq",
      "typeVersion": 1.1,
      "position": [
        820,
        820
      ],
      "credentials": {
        "rabbitmq": {
          "id": "poc4UQ08c1GLjORk",
          "name": "RabbitMQ account"
        }
      }
    }
  ],
  "pinData": {},
  "connections": {
    "When clicking ‘Test workflow’": {
      "main": [
        [
          {
            "node": "Edit Fields",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Edit Fields": {
      "main": [
        [
          {
            "node": "RabbitMQ",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "RabbitMQ Trigger": {
      "main": [
        [
          {
            "node": "RabbitMQ1",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "versionId": "09d1bd6f-6980-482e-80a7-76d1fbf65830",
  "meta": {
    "templateCredsSetupCompleted": true,
    "instanceId": "1b06549ea40930d40bbf0844d3f62a7083d8cbe5e465acde61c9b6fda9870a55"
  },
  "id": "sSFuUAFfIUkqbU7l",
  "tags": []
}

ianpogi5 · 2024-07-08T22:10:57Z

I'm not sure if this is related but the RabbitMQ trigger icon is broken.

netroy · 2024-07-08T22:13:40Z

RabbitMQ trigger icon is broken.

This was fixed 2 weeks ago . Are you on an older version?

ianpogi5 · 2024-07-08T22:36:04Z

RabbitMQ trigger icon is broken.

This was fixed 2 weeks ago . Are you on an older version?

I just upgraded from 1.47.3 from 1.47.2 just now and still got the same error and broken rabbitmq trigger icon(points to png which should be svg just like the action). Disabled browser cache with same error.

Joffcom · 2024-07-09T01:17:53Z

Hey @ianpogi5

The icon issue has been fixed can you try 1.48.0?

ianpogi5 · 2024-07-09T09:26:15Z

Hey @ianpogi5

The icon issue has been fixed can you try 1.48.0?

I have upgraded to 1.48.3. I confirm the icon issue now fixed. But the rabbitmq trigger in test mode is still not working.

Btw after upgrade, I tested the trigger. When I clicked "Test step" button, I see that it creates a consumer connection on rabbitmq. When I click "Stop Listening" in the trigger, the consumer connection doesn't go away. If I do it again, it will again create a new consumer. I think this may point us to where the issue is.

netroy · 2024-07-09T14:57:52Z

I think the issue might be that when we start manually testing a trigger node, and stop it before the node is actually triggered, we were not calling the cleanup function on that node.
This meant that you could end up with open connections and message consumers that could not actually create any executions, but still kept accepting messages.

I've tried to address this in #9980, and created a custom docker image n8nio/n8n:fix-8871.
Can one of you please also pull this docker image and check if this resolves the issue for you?
We can then try to get this merged and released tomorrow 🤞🏽

ianpogi5 · 2024-07-09T22:36:49Z

I think the issue might be that when we start manually testing a trigger node, and stop it before the node is actually triggered, we were not calling the cleanup function on that node. This meant that you could end up with open connections and message consumers that could not actually create any executions, but still kept accepting messages.

I've tried to address this in #9980, and created a custom docker image n8nio/n8n:fix-8871. Can one of you please also pull this docker image and check if this resolves the issue for you? We can then try to get this merged and released tomorrow 🤞🏽

I confirm that the open connections is now gone after I click the stop listening. Thank you very much!

But testing mode still does not work. When clicking test step button, I immediately see in the logs "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function". Then I would see in RabbitMQ that it did got a message:

The Unackowledge becomes 1 but the trigger is still listening. I expect it would stop listening and show the data in output section just like other types of nodes. Let me know if this is correct expectation. When I stop listening, Unack becomes 0 and Ready goes back to 3.

ianpogi5 · 2024-07-09T22:54:41Z

I also tried the option "Delete From Queue When" but same resut.

ianpogi5 · 2024-07-10T13:33:53Z

n8n-nodes-netsuite is pulling in a really old version of n8n-core, and likely messing with the core functionality. Can you please try uninstalling the node, restarting n8n, and checking if that fixes the issue?

If it does, I can send a PR to n8n-nodes-netsuite to update their code.

@netroy thank you for all your help but it would also be great if you can do a PR on 'n8n-nodes-netsuite'.

netroy · 2024-07-11T16:13:25Z

it would also be great if you can do a PR on 'n8n-nodes-netsuite'

drudge/n8n-nodes-netsuite#6

luizeof · 2024-07-24T13:26:26Z

@netroy In version 1.52 the Rabbit Trigger node still does not work.

The connection is opened, the queue item is set to unaked but is not displayed in the N8N interface.

All tests give the same log:

2024-07-24T13:25:00.777Z | error    | There was a problem starting the waiting execution with id "67138": "Only saved workflows can be resumed." "{ executionId: '67138', file: 'WaitTracker.js' }"
2024-07-24T13:25:14.038Z | info     | Started with job ID: 12754 (Execution ID: 415956) "{ file: 'WorkflowRunner.js', function: 'enqueueExecution' }"
2024-07-24T13:25:29.042Z | info     | Started with job ID: 12755 (Execution ID: 415957) "{ file: 'WorkflowRunner.js', function: 'enqueueExecution' }"
2024-07-24T13:25:29.195Z | info     | Started with job ID: 12756 (Execution ID: 415954) "{ file: 'WorkflowRunner.js', function: 'enqueueExecution' }"

Joffcom · 2024-07-24T15:09:07Z

Hey @luizeof,

I have just given this a test and I can confirm it is working in 1.52

Are you able to share your full workflow and how you have n8n configured as it may be something else, In your log snippet which like is for the RabbitMQ test are you also testing this with a wait?

luizeof · 2024-07-24T15:30:19Z

Simple Workflow

The Workflow only has the Rabbit node to isolate the test

The connection is made in rabbit and the item is fetched

But it is not displayed on the interface.

Using the n8n next docker image, without custom nodes.

This message is displayed in the editor container, no error message appears in the worker:

2024-07-24T15:24:30.918Z | error    | There was a problem with the RabbitMQ Trigger node "RabbitMQ Trigger" in workflow "REOOmdtQpPJGaTCZ": "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function" "{\n  node: 'RabbitMQ Trigger',\n  workflowId: 'REOOmdtQpPJGaTCZ',\n  file: 'LoggerProxy.js',\n  function: 'exports.error'\n}"

netroy · 2024-07-24T15:35:47Z

@luizeof Can you reproduce this error right after restarting the instance?

netroy · 2024-07-24T15:37:58Z

Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit error would me that you somehow have an open consumer from a previous manual execution or a previous activation, so something is picking up messages, but that something doesn't have access to the execution context anymore.

This was the exact same thing we fixed in #9980 . So, it's a little perplexing that you are still seeing this 😕

ianpogi5 · 2024-07-25T06:33:55Z

I updated to 1.52.0 and got all the same results as @luizeof

luizeof · 2024-07-26T13:00:02Z

Hi @Joffcom and @ianpogi5 , I did a new installation from scratch with the next image.

Same error, but @Joffcom, in the interface I get a message in the console that could be the problem:

This installation has 1 workflow that has 1 Rabbit Trigger, this message appears as soon as the message is obtained by Rabbit.

The message is obtained in the rabbit, so that it remains as Unaked. It is just not displayed in the interface itself.

barn4k · 2024-07-30T12:07:14Z

Same issue as @luizeof .

My WF setup:
RMQ trigger node with new queue name, assert queue option is enabled. I've run it in the Test mode, then created another WF to send two pinned items there. The first item from it has been collected by the trigger. I've hit the Test mode again and nothing happend. The second item wasn't return, and the trigger seems stuck.

n8n Log:

2024-07-30 14:12:43 2024-07-30T12:12:43.788Z | error    | There was a problem with the RabbitMQ Trigger node "RabbitMQ Trigger" in workflow "2FK2S1aHYGZakNNj": "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function" "{\n  node: 'RabbitMQ Trigger',\n  workflowId: '2FK2S1aHYGZakNNj',\n  file: 'LoggerProxy.js',\n  function: 'exports.error'\n}"

RabbitMQ log when n8n had an issue

2024-07-30 14:12:43 2024-07-30 12:12:43.737039+00:00 [info] <0.1108.0> accepting AMQP connection <0.1108.0> (172.18.0.3:46902 -> 172.18.0.2:5672)

2024-07-30 14:12:43 2024-07-30 12:12:43.784137+00:00 [info] <0.1108.0> connection <0.1108.0> (172.18.0.3:46902 -> 172.18.0.2:5672): user 'user1' authenticated and granted access to vhost '/'

compose file:

version: '3'

services:
  rabbitmq:
    image: rabbitmq:management
    container_name: rabbitmq
    environment:
      - RABBITMQ_DEFAULT_USER=user1
      - RABBITMQ_DEFAULT_PASS=password1
    ports:
      - "5672:5672"
      - "15672:15672"
  n8n:
    image: n8nio/n8n:next
    container_name: n8n_next
    environment:
    - N8N_LOG_LEVEL=debug
    - N8N_LOG_OUTPUT=console,file
    - N8N_SECURE_COOKIE=false
    ports:
    - "5678:5678"
    links:
    - rabbitmq
    volumes:
    - n8n_data:/home/node/.n8n

volumes:
  n8n_data:

networks:
  default:
    driver: bridge

Trigger WF

{
  "meta": {
    "instanceId": "83e1030ad7804421d85e8d13f129b137363ab1ab458054d2a70d6e10b31bf02d"
  },
  "nodes": [
    {
      "parameters": {
        "queue": "myQueue",
        "options": {
          "assertQueue": true
        }
      },
      "id": "26b6e33c-73f5-46f5-97c4-401e437a24e3",
      "name": "RabbitMQ Trigger",
      "type": "n8n-nodes-base.rabbitmqTrigger",
      "typeVersion": 1,
      "position": [
        840,
        420
      ],
      "credentials": {
        "rabbitmq": {
          "id": "RBxe6tOmcdBzIwhT",
          "name": "RabbitMQ account"
        }
      }
    }
  ],
  "connections": {},
  "pinData": {}
}

Sample WF

{
  "meta": {
    "instanceId": "83e1030ad7804421d85e8d13f129b137363ab1ab458054d2a70d6e10b31bf02d"
  },
  "nodes": [
    {
      "parameters": {},
      "id": "1e6ef7de-c305-4329-8a99-2bbce7530801",
      "name": "When clicking ‘Test workflow’",
      "type": "n8n-nodes-base.manualTrigger",
      "position": [
        820,
        380
      ],
      "typeVersion": 1
    },
    {
      "parameters": {
        "queue": "myQueue",
        "options": {}
      },
      "id": "3154b647-0c0b-411e-89c8-7c4f0ef37ff3",
      "name": "RabbitMQ",
      "type": "n8n-nodes-base.rabbitmq",
      "typeVersion": 1.1,
      "position": [
        1000,
        380
      ],
      "credentials": {
        "rabbitmq": {
          "id": "RBxe6tOmcdBzIwhT",
          "name": "RabbitMQ account"
        }
      }
    }
  ],
  "connections": {
    "When clicking ‘Test workflow’": {
      "main": [
        [
          {
            "node": "RabbitMQ",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {
    "When clicking ‘Test workflow’": [
      {
        "name": "First item",
        "code": 1
      },
      {
        "name": "Second item",
        "code": 2
      }
    ]
  }
}

Restarted the n8n and the situation is the same:

first item - collected normally in TEST mode
second item - stucked, error in the log and infinite loop on the node in the UI

netroy · 2024-07-30T20:00:03Z

I'm finally able to reproduce this.

put a message in the queue first
manually test the rabbitmq trigger node

This fails because we are starting the rabbitmq consumer before .emit is assigned to triggerResponse here.
When there are no messages in the queue before a manual trigger, .emit gets assigned correctly though.
So to fix this we need to make sure that the either the consumer starts after the .emit assignment, or consumer starts whenever, but calls .emit only after the assignment.

galdianoo · 2024-08-21T02:02:40Z

hello, any time line to fix the bug in this node?
for me it holds forever and do not output anything. no answer, nor error.

Edit ago, 22th: in portainer logs I have the following errors in loop. version 1.52.2 running on docker swarm 27.1.2 in test mode:

There was a problem with the RabbitMQ Trigger node "RabbitMQ Trigger1" in workflow "PXV8z92cNFHdjSAm": "Overwrite NodeExecuteFunctions.getExecuteTriggerFunctions.emit function"
Attempt to read execution was blocked due to insufficient permissions

running live, it consumes the queue correctly, but not working in test mode makes it hard to debug and build new flows.

stephen-galea-weavr · 2024-09-04T07:33:51Z

Any update on this please? It's a pain to design workflows without test mode.

netroy · 2024-09-04T13:52:15Z

This will be fixed in #10663

janober · 2024-09-05T10:44:44Z

Fix got released with n8n@1.58.0

stephen-galea-weavr · 2024-09-05T10:47:49Z

Thank you!

Joffcom added the in linear Issue or PR has been created in Linear for internal review label Mar 13, 2024

Joffcom mentioned this issue May 13, 2024

fix(RabbitMQ Trigger Node): Fix issue where queue was not created #9378

Closed

Joffcom mentioned this issue May 16, 2024

fix(RabbitMQ Node): Revert breaking change and add option to assert queue / exchange #9422

Open

netroy mentioned this issue Jul 9, 2024

fix(core): Aborting manual trigger tests should call closeFunction #9980

Merged

2 tasks

netroy mentioned this issue Sep 4, 2024

refactor(RabbitMQ Trigger Node): Improve type-safety, add tests, and fix issues with manual triggers #10663

Merged

2 tasks

janober added the Released label Sep 5, 2024

netroy closed this as completed Sep 5, 2024

Rabbit MQ triggers do not work in test mode #8871

Rabbit MQ triggers do not work in test mode #8871

Comments

DRIMOL commented Mar 12, 2024

Bug Description

To Reproduce

Expected behavior

Operating System

n8n Version

Node.js Version

Database

Execution mode

Joffcom commented Mar 13, 2024

DRIMOL commented Mar 13, 2024

Joffcom commented Mar 13, 2024

DRIMOL commented Mar 20, 2024

Joffcom commented Mar 21, 2024

barn4k commented Apr 11, 2024

barn4k commented May 10, 2024

Joffcom commented May 13, 2024

Joffcom commented May 13, 2024

barn4k commented May 15, 2024

Joffcom commented May 15, 2024

barn4k commented May 16, 2024

DRIMOL commented May 16, 2024

DRIMOL commented May 16, 2024

DRIMOL commented Jun 6, 2024

luizeof commented Jun 6, 2024

ramonmatosweb commented Jun 6, 2024

Joffcom commented Jun 27, 2024

DRIMOL commented Jul 1, 2024

netroy commented Jul 1, 2024

DRIMOL commented Jul 1, 2024

netroy commented Jul 1, 2024

DRIMOL commented Jul 1, 2024

ianpogi5 commented Jul 8, 2024

netroy commented Jul 8, 2024

ianpogi5 commented Jul 8, 2024

netroy commented Jul 8, 2024

netroy commented Jul 8, 2024

ianpogi5 commented Jul 8, 2024

ianpogi5 commented Jul 8, 2024

netroy commented Jul 8, 2024

ianpogi5 commented Jul 8, 2024

Joffcom commented Jul 9, 2024

ianpogi5 commented Jul 9, 2024

netroy commented Jul 9, 2024

ianpogi5 commented Jul 9, 2024

ianpogi5 commented Jul 9, 2024

ianpogi5 commented Jul 10, 2024

netroy commented Jul 11, 2024

luizeof commented Jul 24, 2024

Joffcom commented Jul 24, 2024

luizeof commented Jul 24, 2024

netroy commented Jul 24, 2024

netroy commented Jul 24, 2024

ianpogi5 commented Jul 25, 2024

luizeof commented Jul 26, 2024 • edited Loading

barn4k commented Jul 30, 2024 • edited Loading

netroy commented Jul 30, 2024 • edited Loading

galdianoo commented Aug 21, 2024 • edited Loading

stephen-galea-weavr commented Sep 4, 2024

netroy commented Sep 4, 2024

janober commented Sep 5, 2024

stephen-galea-weavr commented Sep 5, 2024

luizeof commented Jul 26, 2024 •

edited

Loading

barn4k commented Jul 30, 2024 •

edited

Loading

netroy commented Jul 30, 2024 •

edited

Loading

galdianoo commented Aug 21, 2024 •

edited

Loading