← All updates Databricks Update One-Pager Navy version
databricks Platform · Updated Jul 4, 2025

Parent tasks (Run job and For each) now have a separate limit

Tasks that wait on child processes (Run job and For each tasks) now have a separate limit for the number of tasks that can run simultaneously, and do not count against the overall limit.

What it does

Tasks that wait on child processes (Run job and For each tasks) now have a separate limit for the number of tasks that can run simultaneously, and do not count against the overall limit. The following tables list various numerical limits for Databricks resources. For additional information about Databricks resource limits, see each individual resource's overview documentation.

Why it matters

Reduces operational overhead and unlocks new capabilities for data teams on Databricks.

Architecture
Databricks Platform → Platform
In short

Tasks that wait on child processes (Run job and For each tasks) now have a separate limit for the number of tasks that can run simultaneously, and do not count against the overall limit. The following tables list various numerical limits for Databricks…

Read the full documentation ↗
Key takeaway
Tasks that wait on child processes (Run job and For each tasks) now have a separate limit for the number of tasks that can run simultaneously, and do not count against the overall limit.
2025-07-04-parent-tasks-run-job-and-for-each-now-have-a-separate-limit Generated by the Databricks Updates Agent · browse all updates