Snowflake ADBC connector error: Error: ADBC: [Snowflake] arrow/ipc:undefined

Hi everyone,

For 2 days, I've receive this error message with a daily refresh in Power BI Service for a semantic model:

DataSource.Error: ADBC: [Snowflake] arrow/ipc: could not read message body: read tcp 10.0.4.xx:xxxxx->3.5.xxx.xxx:xxx: wsarecv: An existing connection was forcibly closed by the remote host.. Microsoft.Data.Mashup.ErrorCode = 10941. Microsoft.Data.Mashup.ValueError.DataSourceKind = Snowflake. DataSourcePath = xxx.eu-central-1.snowflakecomputing.com;FR_WH_PRD. . The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: F_ELEC_CONSUMPTION. Partition: F_ELEC_CONSUMPTION. 0xC14700F0: {"RootActivityId":"XXX"}

Context: the semantic model is connected directly to snowflake database using the PowerQuery Connector without any implementation (because it's an "old" dataset). It retrieves some Snowflake views. One of them contains about 20,000,000 rows (since the beginning of the project). I connect the semantic model with a cloud connection with a service account with Key Pair.

With the error message, I undestand that the issue is a timeout on Power BI Service side to resolve queries caused by the ADBC driver. On the Snowflake side, no problem with this log (no timeout with the queries sent).

I've tried to force the connector from nothing (ADBC by default?) to Implementation = "2.0" (with Key Pair) => same issue.

I've tried to force the Implementation = "1.0" (I think the ODBC driver) with SSO (personnal account). Curioulsy, it works (with the same duration of the last successful refresh).

With SSO, I think you can go back to an ODBC driver. But with a Key Pair identification, it's obligatory to have the ADBC driver...

Other Datasets (with less data) connected with Key Pair work fine in Import or DirectQuery mode, no matter.