Snowflake Statement Timeout

Error Summary

• Hevo could not load data into your Snowflake Destination because the SQL statement used to load the data exceeded the maximum execution time configured in Snowflake.

Potential Causes

Snowflake uses the STATEMENT_TIMEOUT_IN_SECONDS setting to control the maximum time a SQL statement can run. By default, this value is 172,800 seconds (2 days). This limit can be set at the account, user, warehouse, or session level. If the SQL statement that Hevo uses to load data exceeds this limit, Snowflake automatically cancels it.

A SQL statement may take longer than the configured limit if:

• A large volume of data is being loaded.

• The Snowflake warehouse is too small for the workload.

• The warehouse is processing multiple queries simultaneously.

Suggested Action(s)

• Check the STATEMENT_TIMEOUT_IN_SECONDS value at the account, user, session, and warehouse levels using the following commands:

  SHOW PARAMETERS LIKE 'STATEMENT_TIMEOUT_IN_SECONDS' IN ACCOUNT;
  SHOW PARAMETERS LIKE 'STATEMENT_TIMEOUT_IN_SECONDS' IN USER <snowflake_user_name>;
  SHOW PARAMETERS LIKE 'STATEMENT_TIMEOUT_IN_SECONDS' IN SESSION;
  SHOW PARAMETERS LIKE 'STATEMENT_TIMEOUT_IN_SECONDS' IN WAREHOUSE <snowflake_warehouse_name>
  

  Replace the placeholder values in the commands with your own.

  Snowflake enforces the lowest configured value across all levels where this parameter is set. If a stricter (lower) timeout is enforced at the account, warehouse, or session level, that value will be applied. Once you identify the level enforcing the timeout, increase the STATEMENT_TIMEOUT_IN_SECONDS value using the following commands:

  Note: There is no universal recommended value. The right timeout depends on your warehouse size, data volume, and workload.

  • Account level: You must have the ACCOUNTADMIN role to run the command.

    ALTER ACCOUNT SET STATEMENT_TIMEOUT_IN_SECONDS = 180000;
    

  • User level: You can set the parameter for your own user. To modify another user’s parameters, you must have the OWNERSHIP privilege on that user.

    ALTER USER <snowflake_user_name> SET STATEMENT_TIMEOUT_IN_SECONDS = 180000;
    

  • Warehouse level: You must have the MODIFY or OWNERSHIP privilege on the warehouse.

    ALTER WAREHOUSE <snowflake_warehouse_name> SET STATEMENT_TIMEOUT_IN_SECONDS = 180000;
    

  • Session level:

    ALTER SESSION SET STATEMENT_TIMEOUT_IN_SECONDS = 180000;
    

    Replace the placeholder values in the commands with your own.

• If increasing the timeout does not resolve the issue, increase the size of your Snowflake warehouse. A larger warehouse can improve query performance and provide more compute resources, allowing the SQL statement to complete within the configured timeout.

Revision History