Email Trigger (IMAP) had to be deactivated

Describe the problem/error/question

I have an error workflow to monitor regular workflows and I’m getting almost daily a few error messages about the Email Trgger node.
I don’t know the exact reason for the error. It’s totally fine if there are a few times per day when the Email Trigger node maybe can’t reach the IMAP server, but I don’t need an error message then.
I even tried to set “Force Reconnect Every Minutes to 1” but it doesn’t seem to be the solution.

What is the error message (if any)?

{
  "error": {
    "message": "There was a problem with the trigger node \"Email Trigger (IMAP)\", for that reason did the workflow had to be deactivated",
    "timestamp": 1749192018219,
    "name": "WorkflowActivationError",
    "context": {},
    "cause": {}
  },
  "mode": "trigger"
}

Please share your workflow

I’m simply using the Email Trigger (IMAP) node in a couple of workflows like that:

Information on your n8n setup

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

fyi:
I have a second n8n server with another workflow but using the same IMAP server and there are some more information about the error:

{
  "error": {
    "message": "There was a problem with the trigger node \"Email Trigger (IMAP)\", for that reason did the workflow had to be deactivated",
    "timestamp": 1749172822080,
    "name": "WorkflowActivationError",
    "context": {},
    "cause": {
      "errno": -104,
      "code": "ECONNRESET",
      "syscall": "read",
      "source": "socket"
    }
  },
  "mode": "trigger"
}

Why don’t you use the Community Node for messages? I used to get some errors with the IMAP node too. There’s one called: n8n-nodes-imap

I tried this right now, but afaik I can’t use it as trigger node unfortunately.

Is there another one or anonther solution?

Depends on what you wanna do. Maybe you can use a cron trigger and just specify how often it should run.

But if I do so and run it every minute, I have just 86.400 executions a day just in this single workflow…