Error: credentialTypes.reduce is not a function

Questions
1

Describe the problem/error/question

After upgrading from 2.6.3 to 2.6.4 i started to receive an error whenever i load any workflow canvas (even a blank new one with no nodes)
Error pops up as:
Init Problem
There was a problem loading init date: credentialTypes.reduce is not a function

I have cleared browser cache and attempted an alternate browser as well and the error persists

What is the error message (if any)?

Init Problem
There was a problem loading init date: credentialTypes.reduce is not a function

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: 2.6.4
  • Database (default: SQLite): postgressql
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker/gcp
  • Operating system: gcp cloud run serverless

image
image1704Ă—901 59 KB

2

Hi @spyder ,

This error (credentialTypes.reduce is not a function) almost always means the backend is sending broken data to the frontend, and 9 times out of 10, it’s caused by a Community Node or Custom Node that isn’t compatible with the new version.

If you have any custom nodes installed (check your custom folder or package.json if you’re building a custom image), one of them likely has a bad credential definition that’s crashing the API response.

To fix it:

  1. Check your Cloud Run logs. You’ll probably see a warning like “Error loading credential type…” right before the server starts.
  2. If you can, try removing your custom nodes/community nodes and restarting.
  3. Since you’re on Cloud Run, the quickest fix to get back online is just to change your Docker image tag back to 2.6.3 until you figure out which node is the culprit.

If my answer helped solve your question, would you mind marking it as the solution?

It’ll help others find it more easily—and I’d really appreciate it!

3

Hi @spyder Just upgrade to the latest version n8n@next and this issue would be resolved.

4

This is a production environment and I cannot push it past the stable branch at this time per our policy

5

Since you cannot upgrade to a newer version and you are in a production environment, your best immediate move is to rollback.
Update your Cloud Run revision to pull the n8n/n8n:2.6.3 image tag instead of latest or 2.6.4.

6

It appears that what was the next branch (2.7.3) has now become the stable branch. I will update now and see how it goes.

2 Likes