How to Prevent or Retry a Snowflake Execute SQL Query Step when Facing a Suspected Transient Network Error?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

I got this error and stack trace on a Snowflake Execute SQL Query step. It isn’t a credential or syntax issue - the query ran fine when I did it myself, and the query immediately before it ran fine as well. I suspect a transient network error of some sort. What can I do to prevent this, or retry?

TypeError

fetch failed

Stack trace

    at null.null (node:internal/deps/undici/undici:13185:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at null.execute (/var/task/node_modules/@lambda-v2/component-runtime/src/sqlProxyClient.js:141:20)
    at Object.run (file:///pipedream/dist/code/a3c0968177650aefd04da667683dc338469afdcd60fba817f0327434429f9179/code/actions/execute-sql-query/execute-sql-query.mjs:23:18)
    at null.executeComponent (/var/task/launch_worker.js:316:22)
    at MessagePort.messageHandler (/var/task/launch_worker.js:816:28)
2

Hi , could you share a screenshot of your action & error?

3

Is it possible to share your SQL query also, we would like to reproduce it

4

I don’t remember now which one it was. All of the queries normally work, which is why I suspect this of being a transient issue.