Update removed comunity nodes in the active workflows

Questions
1

Describe the problem/error/question

Hello community,
We are using self hosted n8n and yesterday we made a version update to n8n and our community node in that workflow got removed. Because of that the workflow was throwing an error.

Is it intentional or this is a bug I’m not sure. I just wanted to confirm that the version updates would remove the community nodes. Can you please confim?

Here are some screenshots. It worked again when I downloaded the community node so I don’t have another screenshots.

Screenshot 2023-05-24 at 13.12.36
Screenshot 2023-05-24 at 13.12.361970×316 33.9 KB

Screenshot 2023-05-24 at 13.14.02
Screenshot 2023-05-24 at 13.14.022366×1024 181 KB

Thank you for your response!

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

This could be either because the typeVersion in the node, or more likely the type has changed.

I’d recommend selecting that node, copying, and then pasting into a text editor. Then add a new node of that type to the canvas (this one should work). Do the same and copy into another editor and compare the values.

I had this recently where I changed how I installed community nodes. E.g. my "type": "n8n-nodes-ldap.LDAP" changed to "type": "CUSTOM.LDAP". To fix that, I updated the previous node with the new value, then copy pasted it back to the canvas.

Good luck, would be interesting to know what changed.

3

Hey @Irem_Odemis,

What node was it, What version were you on before the upgrade and what version did you upgrade to? How do you have n8n installed as well is it through Portainer?

4

Hello @Jon

  • What node was it - applyMap? what is it? do we have a link?
  • What version were you on before - 0.225.2
  • what version did you upgrade to - 0.229.0
  • How do you have n8n installed - we build image from n8nio/base NODE_VERSION=16, self hosted k8s
  • we don’t use portainer.

ARG NODE_VERSION=16 FROM n8nio/base:${NODE_VERSION} ARG N8N_VERSION RUN if [ -z “$N8N_VERSION” ] ; then echo “The N8N_VERSION argument is missing!” ; exit 1; fi ENV N8N_VERSION=${N8N_VERSION} ENV NODE_ENV=production RUN set -eux; \ apkArch=“$(apk --print-arch)”; \ case “$apkArch” in \ ‘armv7’) apk --no-cache add --virtual build-dependencies python3 build-base;; \ esac && \ npm install -g --omit=dev n8n@${N8N_VERSION} && \ case “$apkArch” in \ ‘armv7’) apk del build-dependencies;; \ esac && \ find /usr/local/lib/node_modules/n8n -type f -name “.ts" -o -name ".js.map” -o -name “*.vue” | xargs rm && \ rm -rf /root/.npm && \ apk add sqlite ENTRYPOINT [ “node”, “/usr/local/bin/n8n” ]

1 Like
5

Hey @Irem_Odemis,

I wonder if maybe there was a permission change at some point or if the node was accidentally deleted. I will keep an eye out for more reports of this but it is good to know you are still running.

1 Like