Node has no access to credential (1.79.1)

[tealium_mondo]

Describe the problem/error/question

Running a workflow that has worked for weeks, I now get an error: “Node has no access to credential”.

I’ve seen that the other threads on this have all been automatically closed without a solution.

• I am the owner of both the project, workflow, and credential
• I have re-created the credential from scratch multiple times
• I tried re-creating the Node again as it suggests, but no success
• I re-create the node in another workflow, using the same crendential, in the same project, and it works
• The credential IS indeed within the credential list of the node, so I’d assume it DOES have access
• Re-creating the workflow would be quite the bother, plus this is happening with other large workflows.
• The credential is a Header Auth, bearer token
• When triggering the workflow, it doesn’t show the normal animation of going through the nodes, just fails right away.

Also, I export this complete workflow, launch a self-hosted instance, import, re-create the credential, and it works fine. So I suspect that rules out a corrupted workflow.

What is the error message (if any)?

Node has no access to credential

Please share your workflow

Share the output returned by the last node

N/A

Information on your n8n setup

• n8n version: n8n Cloud > 1.79.1 ( I’ve tried Stable and Beta )
• Database (default: SQLite): n8n Cloud
• n8n EXECUTIONS_PROCESS setting (default: own, main): ??? n8n Cloud
• Running n8n via (Docker, npm, n8n cloud, desktop app): n8n Cloud
• Operating system: n8n Cloud

[solomon]

Hey @tealium_mondo,

I hope you already found a way to solve this, but in case you didn’t:

Since importing the workflow seems to fix the problem in another instance, try to do it in the same instance that has the issue.

You mentioned recreating the node in another workflow works. So you could basically copy & paste everything, right?

Please let me know how it goes.

[tealium_mondo]

I swear I did that already, and it still hadn’t worked… but it did just now. Thanks.