An Architect clones a database and all of its objects, including tasks. After the cloning, the tasks stop running. Why is this occurring?

Question

Options

• ATasks cannot be cloned.
• BThe objects that the tasks reference are not fully qualified.
• CCloned tasks are suspended by default and must be manually resumed.
• DThe Architect has insufficient privileges to alter tasks on the cloned database.

• A
  5% (1)
• C
  95% (18)

Explanation

When a Snowflake database (or schema/table) is cloned, any tasks within the cloned object are automatically suspended in the clone. This is intentional behavior to prevent cloned tasks from immediately executing and potentially conflicting with the source tasks, duplicating work, or causing unintended side effects. After cloning, an architect must explicitly resume each cloned task using ALTER TASK <task_name> RESUME. Tasks can be cloned (ruling out A), object references are not the issue (ruling out B), and if the architect has cloning privileges they generally have task management privileges on the clone (ruling out D). The root cause is always the automatic suspension of cloned tasks by design.

No community discussion yet for this question.