microsoft / microsoft/PowerPlatformConnectors

[BUG] Snowflake Integration using COPY INTO Statements

Open
#2,847 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Certified Connector

Name of Connector

Snowflake (Preview)

Describe the bug

Attempting to submit a copy into statement to snowflake via power automate. When submitting the query, I receive an error message of:

The API 'snowflakeip' returned an invalid response for workflow operation 'Submit_SQL_Statement_for_Execution' of type 'OpenApiConnection'. Error details: 'The API operation 'ExecuteSqlStatement' requires the property 'body/data/0/6' to be of type 'String' but is of type 'Null'.'

It looks as though the connector requires there to be data received; however, with a copy into statement, I am only posting data.

Is this a security bug?

Yes, this is a security bug

What is the severity of this bug?

Severity 1 - Connector is broken or there's a very serious issue

To Reproduce

Create a flow that submits a table to snowflake.

Expected behavior

There should be some sort of response message that avoids the error generation so that the flow does not break. Additionally this prevents the ability to write error handling against the completion of the sql component.

Environment summary

Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context

I am able to see that the table is being written to; however, power automate shows this section of the flow as a failed because it is looking for the response data to populate into the body section of the JSON.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Snowflake (Preview) connector and its ExecuteSqlStatement operation, which the issue identifies as failing for COPY INTO statements. Reproduce the flow with a COPY INTO query and inspect how the response is handled; done means Power Automate receives a valid completion response instead of a null-body error.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.