I’m getting random “Internal error” responses from the Send Email node, for no apparent reason.
There’s some talk online about it being an app passwords issue, but some emails are being sent correctly while others error — all using the same email credentials.
I’ve seen this error with Google Workspace, Outlook, and SMTP.com so I don’t think it’s an SMTP server-specific issue.
Should I try enabling “Ignore SSL issues” or that’s unrelated?
Is there a stack trace in the error at all that you can share? I suspect the issue is related to the connection settings but hopefully the trace show more.
Can you turn off the error branch so you get the big error and that should have more information. We have a fix coming out in the next release which should reduce the number of the internal error messages.
I don’t think it is a front end issue based on it being “internal error” so I think it could just be mail provider settings which normally causes an issue.
Hi @Jon, this is kind of related. I’ve been trying out the Microsoft Graph API to send emails instead of SMTP.
When I test the workflow, an email is going out correctly, but the http request node (to send the previously created draft email) is getting this error:
{
"errorMessage": "Internal error",
"errorDetails": {},
"n8nDetails": {
"n8nVersion": "1.47.3 (Cloud)",
"binaryDataMode": "filesystem",
"stackTrace": [
"TypeError: Cannot read properties of undefined (reading 'error')",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:699:64",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1076:20"
]
}
}
To confirm, this error comes from n8n and not the http response?
{
"errorMessage": "No data found for item-index: \"1\"",
"errorDetails": {},
"n8nDetails": {
"itemIndex": 1,
"runIndex": 0,
"parameter": "url",
"time": "7/19/2024, 8:40:58 AM",
"n8nVersion": "1.51.0 (Cloud)",
"binaryDataMode": "filesystem",
"stackTrace": [
"ExpressionError: No data found for item-index: \"1\"",
" at Object.get (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/WorkflowDataProxy.js:307:31)",
" at Proxy.eval (eval at getFunction (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/index.js:24:22), <anonymous>:7:77)",
" at Proxy.eval (eval at getFunction (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/index.js:24:22), <anonymous>:14:3)",
" at Tournament.execute (/usr/local/lib/node_modules/n8n/node_modules/@n8n/tournament/dist/index.js:33:19)",
" at evaluateExpression (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/ExpressionEvaluatorProxy.js:110:16)",
" at Expression.renderExpression (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Expression.js:228:70)",
" at Expression.resolveSimpleParameterValue (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Expression.js:206:34)",
" at Expression.getParameterValue (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Expression.js:290:25)",
" at getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1636:42)",
" at Object.getNodeParameter (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:2354:24)",
" at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/HttpRequest/V1/HttpRequestV1.node.js:612:30)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:728:19)",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:673:51",
" at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1085:20"
]
}
}
Does this mean no items were returned? Here’s the http request node that I’m using to send a draft email:
Thank you @Jon. That’s weird because I see both references show as green, and their values look correct. Plus the email went out so I don’t think the URL or access token could’ve been empty.
The referecnes will only show the first input item, In this case for some reason the node is running more than once and the second run can’t find the data from the node you are calling.
At a guess the aggregate node has more than one output.