Snowflake Insert nodes stopped working after the latest update to 2.17.5. Seems like the statement that is being sent to Snowflake has changed and is causing an error. This is the statement that is now being sent to Snowflake (taken from the history monitoring):
INSERT INTO IDENTIFIER(?)(IDENTIFIER(?),IDENTIFIER(?),IDENTIFIER(?),IDENTIFIER(?),IDENTIFIER(?),IDENTIFIER(?),IDENTIFIER(?)) VALUES (?,?,?,?,?,?,?)
Whereas the statements in previous runs before the update were something like this:
INSERT INTO <correct table name in the structure of [db].[schema].[table]> (<correct columns list, comma separated>) VALUES (?,?,?,?,?,?,?)
Nothing was changed in the flow nor in the data. We’ve created other test flows, and all returned the same results.
There is nothing wrong with the credentials.
Did anyone encounter a similar issue?
What is the error message (if any)?
The error is a Snowflake error, not n8n. The error is being caused by the statement sent by n8n.
Thanks for the reply. As mentioned, there is no issue with the credentials, as the error is on Snowflake’s side - the statement itself is flawed. The same credentials are being used in other Snowflake nodes. Also, as mentioned, neither the flow nor the data itself were changed in the last few days. The only thing that was changed is the n8n version.
I’m not sure we can revert to previous versions, as we’re on a cloud plan.
Bug report was already submitted.
We’re bypassing it now by sending the data as JSON or CSV to a staging bucket instead of a direct insert, and importing the files. Seems like this is a bug.
We are experiencing the same - nothing has changed on our end (credentials, workflows, etc) but all of our workflows that insert into Snowflake are failing as of 2.17.5. Per OP, looks like this was probably the commit that is causing the issue?