Hey @shrey-42, unfortunately I was unable to reproduce this on my end. Based on this similar report from @baflo I suspect this could be related to the EmailReadImap node. However, since the error message is slightly different, it would be of great help if you could identify the workflows on your end running this node and temporarily disable them.