For anyone else who runs into this. I found a solution.
A few days ago, I noticed I was getting those weird failures on another node. Where it just dumps a stack trace (in the original post).
The solution was to delete the workflow, create a new fresh workflow, and copy in the nodes from scratch.
This morning I wondered if that could solve the issue.
So I created a new workflow with just the SES node. And shazam, it worked as expected.
I suspect there must be some sort of weird caching going on somewhere.
I have a sneaking suspicion, that the caching could be on the cloudflare end (we use it as the proxy).
But could it be on the n8n side? It is the only thing I can think of.
And fyi, that original workflow SES node, which is identical, still throws a 403 error.
Strange…
3 Likes