For each: nested JAR task can’t reference upstream taskValues
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2025 08:07 AM - edited 08-22-2025 08:10 AM
I’m creating a For each with a nested JAR task.
init_job (notebook) sets dbutils.jobs.taskValues.set("my_value", ...), and the For each container depends on init_job.
but the UI says: “Reference … can only be used in a task that depends on task 'init_job'.” This seems wrong because the nested task has a transitive dependency via the For each.
If I switch the JAR nested task to Notebook Task, it can read the value correctly. for example:
Is this a bug/known limitation for JAR tasks inside For each?
Labels:
- Labels:
-
Workflows