I am very sorry to hear you are having trouble. I just gave this a go on my end and was able to reproduce the problem. I can no longer exclude a node using something like docker run -it --rm --name n8n -p 5678:5678 -e NODES_EXCLUDE='["n8n-nodes-base.awsSes"]' n8nio/n8n:0.205.0:
Trying this on an earlier version of n8n (such as 0.203.1 using docker run -it --rm --name n8n -p 5678:5678 -e NODES_EXCLUDE='["n8n-nodes-base.awsSes"]' n8nio/n8n:0.203.1) still works:
I suspect this might be related to the changes around lazy-loading nodes in an attempt to use less memory. I shall add this to our engineering backlog for a closer look, perhaps you might want to downgrade to a slightly older version of n8n in the meantime?
Greetings @MutedJam. Thank you for the response. As a temporary work around i will be using v0.203.1. Please let me know if there is a newsletter or something similar where I can be notified once the bug is fixed or about new features.