How to Set Separate Schedule for Snowflake Task DAG Child Nodes

Snowflake Task DAGs by default run all child nodes on the same schedule inherited from the root task. This tutorial presents a workaround for assigning different execution frequencies to individual child tasks within a single DAG. The solution uses a config table to persist a counter state and a stored procedure that increments and checks a modulo-based counter. Proxy 'counter' tasks are inserted before child tasks, calling the stored procedure and passing a boolean signal downstream via SYSTEM$SET_RETURN_VALUE. Child tasks then use a WHEN clause with SYSTEM$GET_PREDECESSOR_RETURN_VALUE to conditionally skip execution. The approach is demonstrated with an hourly root DAG where some reports run every 4 hours and others once daily, with full test-drive examples showing SKIPPED task history entries when conditions aren't met.