-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EmailReadImap workflow randomly stop #3794
Comments
Happened again, now with an another n8n Workflow with an external mail provider, but with EMailReadImap node. Workflow stopped 2022-08-08 17:00:49 Message (when you click the red triangle) Every time this happens, it creates smaller / new log files:
|
Till now since 0.189.1 the problem did not occur again. |
I use a "EmailReadImap" node in many workflows and they reconnect every 5 minutes to different sever.
I can see a reconnect every 5 minutes in the mailservers log-files, so far everything is ok.
n8n sometimes re-initialize all workflows (on cleanup log? or sqlite? i don't know).
But sometimes one workflow with EmailReadImap is not re-initialized.
From log (simplified, without other json-data)
If this happen, the workflow "mail47" is shown as "stopped". But in the mailserver logfile i can still see every 5 minute a reconnection.
When i manually stop workflow "mail47" it is stopped and the server logfile has no further reconnection entry.
The problem occur sometimes when n8n re-initialize the workflows and can't automatically restart one workflow.
It seems that EmailReadImap still runs in background and n8n could not start a new process with that workflow. All other workflow with EmailReadImap restarts.
Then the workflow "mail47" is marked as stopped.
EmailReadImap is still running, it reconnects every 5 minute to the server, but the remaining workflow will not be executed, even if a new email arrive. It only reconnects every 5 minutes, although the workflow is not active.
I use these scripts since 1 year, they run until version XXX without any problem. I updated n8n ~2 month ago so i could not say which version XXX exactly was. The problem occurred since that update. I updated last week to version 0.186.1 and the problem happened now again.
To Reproduce
I can't reproduce it.
What i can say is, that all server run and could be accessed, no blocking, no firewall-problem. There is no other error in any log. Mails come in, mails go out.
Environment
The text was updated successfully, but these errors were encountered: