I have a issue with a Workflow I created. This workflow subscribe to an AWS SNS and send an email to a customer. One day, a sunday, my N8N workflow just stop processing the event.
I don’t understand why but today I try to understand and really I do not.
I have an other Workflow, who subscribe to an other SNS who work just fine, they have the same IAM Users with the same write for information.
I just Deactive the workflow and re-active it and it start processing 2 event and then have the error message that I share.
I don’t understand why they have only few event and then it stop
What is the error message (if any)?
Issues:
The resource you are requesting could not be found ( Sender NotFound Subscription does not exist 667f4962-bd1f-5d49-a144-16d810353c91 )
Execution Error.
Please share your workflow
Information on your n8n setup
n8n version: don’t know how to find the info
n8n EXECUTIONS_PROCESS setting (default: own, main): guess it’s own
Running n8n via (Docker, npm, n8n cloud, desktop app): n8n.cloud
Would you be able to answer the questions below for us?
Can we get the full error message?
Does it always start working again if you re-activate?
Can you share your cloud instance username and we can take a quick look in the logs?
Hi @Jon - I came across this thread as I was about to post the same issue. I’ve been experiencing this for quite some time, but always forget to post because sometimes it doesn’t happen/it is a bit of a gremlin.
For me, it will sometimes occur when saving my workflow that has the SNS trigger, even if I have not modified the SNS trigger node. To halt the infinite error loop, I have to either:
Restart n8n
Disable the SNS Trigger node and save the workflow, then re-enable the SNS trigger node and save the workflow
Simply deactivating the entire workflow and saving, and reactivating does NOT resolve the issue (it resumes the continual errors upon workflow activation).
My n8n environment
n8n version: 1.72.1 (though I have observed this for quite some time, probably since 1.4 at least)
Running n8n via (Docker, npm, n8n cloud, desktop app): docker on AWS arm64
Complete node error message
(I’m not worried about specific endpoints/names disclosed here)
{
"errorMessage": "The resource you are requesting could not be found",
"errorDescription": "<ErrorResponse xmlns=\"http://sns.amazonaws.com/doc/2010-03-31/\">\n <Error>\n <Type>Sender</Type>\n <Code>NotFound</Code>\n <Message>Subscription does not exist</Message>\n </Error>\n <RequestId>101d415b-b684-51be-916f-1ead448a5af7</RequestId>\n</ErrorResponse>\n",
"errorDetails": {
"rawErrorMessage": [
"404 - \"<ErrorResponse xmlns=\\\"http://sns.amazonaws.com/doc/2010-03-31/\\\">\\n <Error>\\n <Type>Sender</Type>\\n <Code>NotFound</Code>\\n <Message>Subscription does not exist</Message>\\n </Error>\\n <RequestId>101d415b-b684-51be-916f-1ead448a5af7</RequestId>\\n</ErrorResponse>\\n\""
],
"httpCode": "404"
},
"n8nDetails": {
"nodeName": "SNS: FENZ-AMS-Notifications-Email",
"nodeType": "n8n-nodes-base.awsSnsTrigger",
"nodeVersion": 1,
"time": "1/7/2025, 10:11:42 PM",
"n8nVersion": "1.72.1 (Self Hosted)",
"binaryDataMode": "default",
"stackTrace": [
"NodeApiError: The resource you are requesting could not be found",
" at WebhookContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1297:19)",
" at processTicksAndRejections (node:internal/process/task_queues:95:5)",
" at WebhookContext.requestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1567:20)",
" at WebhookContext.awsApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/GenericFunctions.js:22:16)",
" at WebhookContext.awsApiRequestSOAP (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/GenericFunctions.js:38:22)",
" at WebhookContext.webhook (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/AwsSnsTrigger.node.js:201:13)",
" at Workflow.runWebhook (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:679:15)",
" at Object.executeWebhook (/usr/local/lib/node_modules/n8n/dist/webhooks/webhook-helpers.js:155:33)"
]
}
}
Complete SNS trigger node source
(I’m not worried about specific endpoints/names disclosed here)
I have basically the same issue. It is kind of intermittent, some notifications come through, but then I get the error multiple times. My exact error message:
The resource you are requesting could not be found
Sender NotFound Subscription does not exist ef6d2088-e295-512c-9c9c-408514659a85
I am currently at n8n version 1.58.2 using docker image in queue mode
In case my Sentry DSN info can be used to debug this, I just had a slew of these occur.
86 errors within a few seconds/minutes around time Wed 5 Feb 2025 04:08:11 UTC
The SNS topic it attempts each time is different, so I’m guessing it is creating the subscription and maybe hitting a race condition where it can’t subscribe to it right away, then it repeats and keeps trying over and over?
One SNS topic ID from a random error in this occurance was 53310263-7cc9-5d9f-bd6d-627f9bed310d
My n8n instance ID throwing the errors is 8821b6815d423f94ca3261ccb8daa88d8162f35a286bdb613bcd9534e9613ea7