We don’t directly support community nodes but I can take a quick look. Which version of the node are you using and did you install it from the UI or with a custom docker image?
Hi @Jon I did some testing and it seems that if the db is SQLite(remove all DB_ from above docker compose), everything works fine. Restarting the container does not cause n8n-nodes-netsuite to become unrecognized.
If I use posgresql as db, the error happens everytime I restart the container. Seems like an n8n issue.
The root cause of this issue was that I installed n8n-nodes-netsuite twice(install-uninstall-install) which has caused the type value to be n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite. Then I created my workflows which now contain the type n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite. Every time n8n restarts, my n8n-nodes-netsuite and the workflows that contain that node become unrecognized.
The solution that I did was to edit directly in the database all type with value n8n-nodes-netsuite.n8n-nodes-netsuite.netsuite and change it to n8n-nodes-netsuite.netsuite.
I still don’t know if it’s an n8n or n8n-nodes-netsuite bug that causes the incorrect type. This issue can be easily replicated using the above steps.