Hi @ChristianRRL,

No. Lakeflow Jobs don’t support a child job/task setting or updating a parent job’s task values. 

dbutils.jobs.taskValues.set() always writes a value for the current task in the current job run. There is no way to target a different task or a different job (like the Run Job parent).

Run Job creates a separate job run. Its task values remain scoped to that child job and cannot become the task values of the parent’s Run Job task, nor can they be read by a sibling Run Job (your Parent 2).

To get your pattern working, you still need to either move Child 1 into the same Lakeflow job as Parent 2 and use task values normally, or have Child 1 persist output_path to UC-managed storage, then in the parent job read it and re-expose it via dbutils.jobs.taskValues.set, which Parent 2 and its children can then reference.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.