Imap Trigger - No 2 can work simultaneously

Hi all,

Currently running into an issue with some of my N8N flows.

Describe the problem/error/question

I have 2 workflows, that are exactly the same, starting with an IMAP trigger. The only difference is that they are triggered by 2 different email addresses.
The thing is only one seems to be working. Let say I have [email protected] and [email protected]

→ Both workflows are active
→ If I run a test on one of the workflow, let say email1, the test goes well, and the result is that only this workflow will effectively be triggered by new emails
→ If I now run a test on email2, email1 will stay active, but in reality, emails will just be set as ‘read’, and nothing else will happen on this workflow, whereas email2 will now be running well.

So I can’t have both workflows running at the same time, I don’t understand why. The only workflow that will work will be the last one I’ve run a ‘test’ on, the other one will stay active but in reality just mark emails as seen, without performing any action…

I’ve been reading multiple topics on the forum, especially from 2024, and IMAP seems to be a hot topic… But never seen something similar.

Any idea of potential bug/mistake I’ve made or how to solve this?

Thanks a lot for your help

Please share your workflow

Information on your n8n setup

  • n8n version: 1.83.2
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Own
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system:

hello @joco

are you using the same credentials for both nodes or different?

Hi @barn4k

I’m using 2 different credentials (2 different email addresses)

Hi, do you still have the issue if you remove any filters. I know it’s stupid for your use case but just to understand whether the trigger works

Reg,
J.

Can you turn on the debug logs and send them when the issue is occuring?

To enable debug logs, please run the docker container with additional ENV variable N8N_LOG_LEVEL=Debug. Then you can see the logs with docker command docker logs container_id/name or via docker GUI

@barn4k

Thanks for your reply!

I’ve edited my docker-compose.yml file (don’t have an .env file).

But then, when I check the logs, I don’t see anything when triggering the email used in the workflow that is currently not working. I’ve tried 4 times, all the emails are marked as ‘SEEN’, but nothing else.

Any clue?

I can’t see any log when triggering the workflow that is working well…

hm… can’t say what may be wrong. Can you try updating to the latest stable version?

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