Thanks for the reply @Jon. I’m running version 0.222.0 in Docker on my Synology NAS. I’ve removed and re-added the IMAP node several times and also tried duplicating the workflow as some others seemed to have success with that but I had no luck. it just always marked the incoming mail as read and went no further in the flow. I’ve since deleted it and changed to the ‘Gmail Trigger’ instead which is doing what I need now perfectly.
Hey @McPhisto,
That is interesting to hear keep an eye on the gmail trigger node and let me know if that continues to work, I just double checked the code for the other node and it should be marked as processed once completed so it sounds like something went wrong in the middle.
I wonder if it was specific emails causing it to trip up, I will have a think about more debug options we could add for the future.
1 Like
Hi,
i’m assuming this is still an ongoing issue. i looked for other newer threads and they’re still pointing to this thread.
i do have the same issue with Gmail trigger. the email is marked as read, but following nodes are not being processed. i also enabled the option to save successful trigger, however i’m not seeing any runs.
Same situation here, client just send me E-Mail and it should go to discord but executions are blank.
When im testing sometimes it working sometimes no.
Hey @baraapro,
Welcome to the community 
I have not seen the gmail trigger fail in the same way as it works in a different way. Are you sure you are using the gmail trigger and not the imap node?
Can confirm that IMAP node has some issues. Using latest version of everything with default sqlite database. Manual installation with npm setup, running as a systemd service.
I’m using 5 workflows which are checking 5 different mailboxes on the same provider.
1st workflow as a prototype works fine.
So I’ve duplicated 1st workflow 4 times and changed credentials for each mailbox. Activated the workflows and only original prototype works. Log file set to debug and there is no error. No executions are visible in UI.
Tried activating just one of the new workflows, to see that maybe running multiple is an issue, that is not the case.
The new ones simply do nothing, debug looks like this (this is parsed json for readability) :
‘2024-02-01T16:35:49.132Z’ ’ => Started’
‘2024-02-01T16:35:49.132Z’ ’ - “LISS Check email create issue” (ID: sPEttMGkzHWXfu92)’
‘2024-02-01T16:35:49.132Z’ ‘Initializing active workflow “LISS Check email create issue” (ID: sPEttMGkzHWXfu92) (startup)’
‘2024-02-01T16:35:49.134Z’ ‘Adding triggers and pollers for workflow ““LISS Check email create issue” (ID: sPEttMGkzHWXfu92)”’
‘2024-02-01T16:35:49.141Z’ ‘Loaded static data for node “EmailReadImap”’
‘2024-02-01T16:35:49.405Z’ ‘Querying for new messages on node “EmailReadImap”’
‘2024-02-01T16:35:49.406Z’ ‘Workflow “LISS Check email create issue” (ID: sPEttMGkzHWXfu92) activated’
‘2024-02-01T16:35:49.408Z’ ‘Successfully started workflow “LISS Check email create issue” (ID: sPEttMGkzHWXfu92)’
…
‘2024-02-01T16:35:49.559Z’ ‘Email Read Imap:update 3’
…
‘2024-02-01T16:36:46.999Z’ ‘Wait tracker querying database for waiting executions’
‘2024-02-01T16:37:46.999Z’ ‘Wait tracker querying database for waiting executions’
‘2024-02-01T16:38:47.000Z’ ‘Wait tracker querying database for waiting executions’
Emails in mailbox are not marked as read. After couple restarts, activate/deactivate sometimes emails are marked as read, sometimes not, however there’s nothing in executions or debug log file except for lines like
‘2024-02-01T16:35:49.559Z’ ‘Email Read Imap:update 3’.
All manual “test” executions work, unread emails are processed, no errors are visible anywhere.
1st manually created original works as it should (almost insta trigger when email arrives) no matter how many others are active. The copies (only difference is credentials, otherwise identical) do nothing.
Figured it out, in case anyone works with multiple mailboxes and uses Duplicate workflow with IMAP node trigger.
Duplicate function copies some data that tracks IMAP messages. Everything kinda breaks when there’s discrepancy between expected value and message counter/state from server.
To fix this, after duplicating your workflow:
Stop n8n instance and go to your n8n database, in case of default sqlite theres a file called database.sqlite in .n8n folder.
Browse table “workflow_entity” and locate problematic workflow, theres a column called “name” to identify.
Set corresponding column “staticData” to NULL in your sql editor, it has to be NULL as in database NULL, not just empty value - n8n won’t start with empty. Start n8n and it will get proper values from IMAP server, works afterwards as expected.
1 Like
Hello community!
I came across the same error today (v 1.42.1) - the IMAP node would not go beyond simply marking the e-mails as “read”. It was created as a duplicate of another workflow.
Solution: Start a new workflow, add IMAP trigger manually and then copy-paste the rest of the workflow.
2 Likes
Same problem here with 1.61.0. Changing the value of column “staticData” to “NULL” worked for me. Thanks