IMAP gets triggered twice about 50% OF THE TIME

[JonathanTAU]

Describe the problem/error/question

The trigger for my workflow is the imap node. It always triggers twice. In the beginning it worked normally. Then it started. I switched to a new emailadress and same thing, after 1-2 weeks it suddenly started. The workflow is always triggered twice. Very annoying and client is not happy.
I was able to reproduce this in a workflow with only the imap trigger node and nothing else, so it’s just about the node. I also reproduced it on cloud-n8n version and a local version.

Correction: It’s pretty random, I’d say it gets triggered twice 50% of the time and I can’t see a pattern.

Please share your workflow

{
“nodes”: [
{
“parameters”: {
“format”: “resolved”,
“options”: {}
},
“type”: “n8n-nodes-base.emailReadImap”,
“typeVersion”: 2.1,
“position”: [
688,
3568
],
“id”: “aef03974-a34a-43bb-960d-76d417b60b29”,
“name”: “Email Trigger (IMAP)”,
“credentials”: {
“imap”: {
“id”: “EfimE50TvZmmi4HF”,
“name”: “ticketerstellung”
}
}
}
],
“connections”: {
“Email Trigger (IMAP)”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“templateCredsSetupCompleted”: true,
“instanceId”: “43eb8da2d6218989e7e7c2fdcf208e6d53d2874239d8464868ebfd1cbcb81ed1”
}
}

Share the output returned by the last node

{
“nodes”: [
{
“parameters”: {
“format”: “resolved”,
“options”: {}
},
“type”: “n8n-nodes-base.emailReadImap”,
“typeVersion”: 2.1,
“position”: [
688,
3568
],
“id”: “aef03974-a34a-43bb-960d-76d417b60b29”,
“name”: “Email Trigger (IMAP)”,
“credentials”: {
“imap”: {
“id”: “EfimE50TvZmmi4HF”,
“name”: “ticketerstellung”
}
}
}
],
“connections”: {
“Email Trigger (IMAP)”: {
“main”: [

]
}
},
“pinData”: {},
“meta”: {
“instanceId”: “43eb8da2d6218989e7e7c2fdcf208e6d53d2874239d8464868ebfd1cbcb81ed1”
}
}

Information on your n8n setup

• n8n version: latest
• Database (Postgres):
• Running n8n via (Docker):
• Operating system: Ubuntu

[King_Samuel_David]

Hey, @JonathanTAU

I;ve seen this before come up, the only solution was creating a new workflow, and copying the orginal into it. Have you tried this?

Please let me know if this resolves it.

Samuel

[JonathanTAU]

Yeah it does, also restarting the workspace helped. It’s something about a second n8n-worker (from an older version of the workflow) working in parallel. Basically two workflows were running, and old and a new version.
I’m more curious however about it happens in the first place. Fixing it is easy, but it happened twice so far. Would appreciate any help I can get on this, because we have this running for multiple clients

[Milyn_Dsilva_CC]

Any solutions ? this is a real issue, copying wf to a new one might work but its not a real fix

[JonathanTAU]

Solution was to restart the VPS I used to self-host. Something about multiple “runners” being active at the same time. So basically we had the current version of the workflow and some “ghostly” past (older) version that was also running. Restarting the VPS caused the “ghost” runner to disapper. Had to do this a couple of times since then because the problem kept reappearing sometimes when we updated the workflow.