For serverless tasks, Snowflake automatically scales resources to make sure tasks complete within a target completion interval, including queueing time. For user-managed tasks, longer queueing …

Snowflake guarantees that at most one instance of a task with a defined schedule is running at a given time; however, we cannot provide the same guarantee for tasks with a defined predecessor task.

When the root task in a task graph is resumed or manually executed, Snowflake sets a version of the entire task graph, including all properties for all tasks in the task graph.

Snowflake estimates the resources needed using the target completion interval, and adjusts to complete the task in this time. The following example creates a serverless triggered task that runs whenever …

Lists the tasks for which you have access privileges. The command can be used to list tasks for the current/specified database or schema, or across your entire account.

Select a task on the graph to view additional details, such as predecessor tasks, the warehouse used to run the task, and the role that owns the task. You can also edit the root task to change parameters …

Prerequisites The examples in this topic assume that you’ve added code to connect with Snowflake and to create a Root object from which to use the Snowflake Python APIs. For example, the following …

By default, Snowflake runs tasks by using the system user with the privileges of the task owner role. To run a task as a specific user, configure the task with EXECUTE AS USER.

A task object runs a SQL statement, which can include calls to stored procedures. Tasks can run on a schedule or based on a trigger that you define, such as the arrival of data.

Manage tasks The Snowflake REST Task API provides the following endpoints to access, update, and perform certain actions on task resources in a Snowflake database: