FTP Node Error Not Triggering Error Workflow

Describe the problem/error/question

In one our client we have an FTP node with a “continue on fail” set to true. Initially there was an error with the credential and the problem is that it did not override the output to have an error field containing the error.
The next node (an IF node) got the following message in the input:

The “true” output on the IF node was the input that sent to SFTP node. I would expect this to be recognized as an error.
There is also an error workflow for this workflow which was not triggered.
Why did this error not trigger the error workflow or the IF node? How can I check for this type of error in the future if there is no output?

What is the error message (if any)?

ERROR: Credentials could not be decrypted. The likely reason is that a different “encryptionKey” was used to encrypt the data.

Error: Credentials could not be decrypted. The likely reason is that a different "encryptionKey" was used to encrypt the data.
    at Credentials.getData (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/Credentials.js:41:19)
    at CredentialsHelper.getDecrypted (/usr/local/lib/node_modules/n8n/dist/CredentialsHelper.js:191:51)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at getCredentials (/usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/NodeExecuteFunctions.js:1258:33)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Ftp/Ftp.node.js:425:27)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:658:19)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:631:53

Information on your n8n setup

  • n8n version: 1.8.2

Hi @Tuckan, I am so sorry you’re having trouble with this. I think the problem here would be that the credentials failing to decrypt are not related to the node-specific logic.

Are you also seeing this problem after re-creating your credentials so n8n can read them again?

Also, are you persisting your encryption key from the .n8n directory? The error message would suggest n8n no longer has access to it, depending on when this started happening and depending on how you have deployed n8n this might be a result of this change.

Hi @MutedJam, thank you for checking in.
We managed to resolve the credential issues.
My main concern is that the error was not reported and the workflow continued even though it should have stopped by the IF node.
I would expect that all types of errors will be stopped as it has the risk for the workflow to send out false positive which we cannot have.
Is there any way to track these type of error? Is there any workaround?
For now I disabled “continue on fail” but from what I understand certain types of errors won’t trigger the error workflow so it leaves us in the dark.

Hi @Tuckan, I am so sorry for this. Fwiw, this particular error would trigger an error workflow, but the “Continue on fail” setting of course does not seem to work as expected here.

I shall add this to our internal bug tracker for a closer look.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.