Hi @alejandorr
Yes, retries are supported on Run Job tasks. The Run Job task docs say to configure retries, run-duration or streaming-backlog thresholds, or notifications, see Advanced task settings, the same place youโd set them for a notebook task. So the setting itself isnโt the problem. databricks
The clue is that the retry fields donโt show up in the Jobs API get response. That means they never reached the deployed job, so the parent task has no retry policy to apply. A few things to check:
- Placement in the YAML: max_retries and min_retry_interval_millis belong at the task level, as siblings of run_job_task. If theyโre indented under run_job_task, they wonโt be applied. It should look like this:
yaml
resources:
jobs:
parent_job:
name: parent-job
tasks:
- task_key: call_child
max_retries: 3
min_retry_interval_millis: 60000
retry_on_timeout: false
run_job_task:
job_id: ${resources.jobs.child_job.id}- Check what the bundle actually sends: Run databricks bundle validate --output json and look for max_retries on that task. If itโs missing there, the problem is in the YAML. Also confirm you deployed to the target youโre checking in the API.
- Continuous trigger: If the parent job uses a continuous trigger, task retry policies donโt apply. Continuous jobs use their own retry mode with exponential backoff instead.
- Isolate bundle vs. platform: Add retries to the Run Job task by hand in the UI, then call the get API. If the fields show up, the platform supports it and the issue is in the bundle config.
One design point to keep in mind: a retry on the Run Job task reruns the whole child job, including tasks that already succeeded. If only one task in the child job tends to fail, itโs often better to put retries on that task inside the child job, so only the failing work reruns.