Technical references

Tip: This page includes some tips you may find useful when working with Snowflake activities.

• When you expect your query to result in a large set of rows, always use LIMIT and OFFSET to paginate through your results. Refer to the Snowflake documentation for query examples for this use case.
• Generate Output Schema works successfully only for query statements that do not contain any workflow variables. Once the output schema is generated, you can replace the query with variables. We recommend using a query that you’re successfully able to run in Snowflake directly.
• Use Execute Any Query Asynchronously for any queries that take more than 30 seconds to execute.
• You can execute non-Select commands (such as insert, update, stored procedures, etc.) only with the Execute Any Query Asynchronously activity.
• Use the Get Asynchronous Query Execution Status activity with the query ID obtained from the output of Execute Any Query Asynchronously.
• You can use the Asynchronous Query Status Changed trigger to initiate a process when a query was successfully executed or encountered an error.
• To get the results of an asynchronous query, use the Get Asynchronous Query Execution Result activity. Use the query ID from the output of Execute Any Query Asynchronously to generate the output schema. Once the schema is generated, you can use a variable query ID. Changing the input to a variable does not affect the output properties, which remain the same. This means the generated output can't be changed unless you manually regenerate it. We recommend setting up different workflow processes if needed. If you’re using Studio Desktop, you can use the Native Search activity from Snowflake package version 5.0.1.
• For the Record Created and Record Updated triggers to run successfully, you must execute the following query on the tables you are monitoring for events: ALTER TABLE [TABLE_NAME] SET CHANGE_TRACKING = TRUE;. Additionally, make sure you have the required permissions configured in Snowflake.