[Resolved] Custom node stopped working after upgrading to v0.214.0

[shrey-42]

My custom node (n8n-nodes-directus - npm) stopped working after upgrading to v0.214.0

Has there been some change in the underlying APIs?

If yes, what do we need to change in our custom nodes to accommodate for those changes?
If no, is this a bug?

Information on your n8n setup

• n8n version: 0.214.0
• Database you’re using (default: SQLite): Postgres
• Running n8n with the execution process [own(default), main]: main
• Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker

[Jon]

Hey @shrey-42,

Are you getting any errors?

I just installed the node ok, Is it maybe a functionality thing?

[shrey-42]

Hey @jon, going to try to reproduce this on my local setup now.

Accidentally upgraded the production instance to 0.214.0 and everything stopped working. So, had to immediately roll back without debugging.

[netroy]

@shrey-42 are your workflows using the Custom API Call operation by any chance ?

[shrey-42]

Hey @netroy. No, not in the concerned workflows.

@Jon
Also, the node’s working fine on my local setup.

Some of my backend functionalities are also currently down (due to DO’s massive almost-week long issue in my region). Might be that’s why the workflows stopped working. But don’t know why the icon for the node showed an error sign.

Looks like it might end up being a false scare, as far as n8n is concerned.

Going to upgrade the prod setup again and check.

[Jon]

@shrey-42 perfect, We will stand down

[shrey-42]

Yeah, confirmed that the issue isn’t on n8n’s end.

False scare indeed

Thanks for jumping in promptly!