Same silent failure reported here, but in a very different environment: n8n Cloud v2.34.6, Skymail provider (Brazilian managed solution — not Gmail or self-hosted), IMAP trigger typeVersion 2.1, Resolved format, no custom email rules, and forceReconnect set to 5 minutes instead of the default 45. Low-volume mailbox, so the connection sits idle for hours between messages.
It worked for weeks and stopped triggering without warning — emails arrive and stay unread, the workflow remains marked as published, nothing appears in the executions list, the Error Workflow doesn’t trigger, and manual execution processes the exact same messages without any problem.
Two things I’d like to know:
- Has anyone correlated low
forceReconnectvalues with higher failure incidence? At 5 minutes I run ~288 reconnections per day, and each one is a chance to fall into thehandleReconnectpath that silences both error channels. - Has anyone checked if these crashes coincide with instance restarts from Cloud upgrades? A managed provider can hold the old connection slot for a few minutes after a dirty disconnect, so reconnecting right after a restart might be legitimately refused — and fall into that same silent path.