Hi, I’m getting the error in the headline a few times a minute whenever a workflow is active with the IMAP trigger and a specific email account is connected. The email account in question is the account of a customer.
I woke up one morning to 35.000 emails because the errornotification got triggered all night by this.
I’ve already set the IMAP node to force reconnect every 3 minutes. The main workflow doesn’t actually all the errored executions. It contains only executions from when a new email acctually arrives. And the automation is actually working. That’s the weird part.
It’s the error workflow that is assigned TO this automation which is freaking out and getting all the executions a few times a minute. And contrary to what it says it does not deactivate the main workflow.
We are on the self hosted n8n, Version 1.113.3 and I was able to reproduce this on another self hosted server we also use AND ON THE CLOUD PLAN AS WELL.
The problem exists even if the IMAP trigger is the only node in the workflow. So the problem is really just about this particular account being connected.
I don’t know too much about the email account and the server except that the Host is “exchange2019.ionos.de”
I already asked the person who manages the email server but I also wanted to ask here, in case he can’t help us.
This is the full JSON of the error:
[
{
“trigger”: {
“error”: {
“message”: “There was a problem with the trigger node \“[email protected]\”, for that reason did the workflow had to be deactivated”,
“timestamp”: 1759439168455,
“name”: “WorkflowActivationError”,
“context”: {
}
},
“mode”: “trigger”
},
“workflow”: {
“id”: “3fN6grHfFCojChmn”,
“name”: “pmc-005-emailToTicket-casavi-mainflow(MANUAL)-vers1.00”
}
}
]