<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Access to For Each run ids from jobs rest API in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/91521#M38185</link>
    <description>&lt;P&gt;Hello Community&lt;/P&gt;&lt;P&gt;I'm using the for_each tasks in workflows, but I'm struggling to access to the job information through the job APIs.&lt;/P&gt;&lt;P&gt;In short, using the runs api (&lt;A href="https://docs.databricks.com/api/workspace/jobs/getrun#run_id" target="_blank"&gt;Get a single job run | Jobs API | REST API reference | Databricks on AWS&lt;/A&gt;&lt;SPAN&gt;), I'm able to access the single tasks run IDs of the specific run, when they are sub-jobs.&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"tasks": [{'run_id': XXXXX,...},...]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;In case of &lt;STRONG&gt;for each&lt;/STRONG&gt; tasks, I can access the "root" task (name, run ID, everything), I can access the input parameters used in the sub jobs steps, but &lt;STRONG&gt;I can't access&lt;/STRONG&gt; the run IDs of each iteration (but this information is easily accessible from the databricks portal).&lt;/P&gt;&lt;P&gt;On the other hand, if I get via API the info about such steps using the specific iteration run ID (that I take from the portal), the job is of course there, and it's also connected to the root ID via&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{job_run_id:RUN_ID}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp; Am I missing something? How can I access the iteration run IDs knowing the run ID of the caller?&lt;/P&gt;</description>
    <pubDate>Tue, 24 Sep 2024 07:21:57 GMT</pubDate>
    <dc:creator>N_M</dc:creator>
    <dc:date>2024-09-24T07:21:57Z</dc:date>
    <item>
      <title>Access to For Each run ids from jobs rest API</title>
      <link>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/91521#M38185</link>
      <description>&lt;P&gt;Hello Community&lt;/P&gt;&lt;P&gt;I'm using the for_each tasks in workflows, but I'm struggling to access to the job information through the job APIs.&lt;/P&gt;&lt;P&gt;In short, using the runs api (&lt;A href="https://docs.databricks.com/api/workspace/jobs/getrun#run_id" target="_blank"&gt;Get a single job run | Jobs API | REST API reference | Databricks on AWS&lt;/A&gt;&lt;SPAN&gt;), I'm able to access the single tasks run IDs of the specific run, when they are sub-jobs.&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;"tasks": [{'run_id': XXXXX,...},...]&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;In case of &lt;STRONG&gt;for each&lt;/STRONG&gt; tasks, I can access the "root" task (name, run ID, everything), I can access the input parameters used in the sub jobs steps, but &lt;STRONG&gt;I can't access&lt;/STRONG&gt; the run IDs of each iteration (but this information is easily accessible from the databricks portal).&lt;/P&gt;&lt;P&gt;On the other hand, if I get via API the info about such steps using the specific iteration run ID (that I take from the portal), the job is of course there, and it's also connected to the root ID via&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{job_run_id:RUN_ID}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp; Am I missing something? How can I access the iteration run IDs knowing the run ID of the caller?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 07:21:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/91521#M38185</guid>
      <dc:creator>N_M</dc:creator>
      <dc:date>2024-09-24T07:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: Access to For Each run ids from jobs rest API</title>
      <link>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/91553#M38196</link>
      <description>&lt;P&gt;Small correction:&lt;BR /&gt;Iteration jobs can be connected to root job IDs via the attribute&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{parent_run_id:RUN_ID}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 09:41:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/91553#M38196</guid>
      <dc:creator>N_M</dc:creator>
      <dc:date>2024-09-24T09:41:25Z</dc:date>
    </item>
    <item>
      <title>Re: Access to For Each run ids from jobs rest API</title>
      <link>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/92925#M38584</link>
      <description>&lt;P&gt;I couldn't figure out anything to systematically access for_each tasks. I believe this is a quite important missing piece (unless of course I'm missing something).&lt;BR /&gt;Is there a way to ask to a developer or should I open a ticket through my company?&lt;/P&gt;</description>
      <pubDate>Mon, 07 Oct 2024 09:58:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/92925#M38584</guid>
      <dc:creator>N_M</dc:creator>
      <dc:date>2024-10-07T09:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Access to For Each run ids from jobs rest API</title>
      <link>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/128695#M48319</link>
      <description>&lt;P&gt;This feature would be extremely helpful in monitoring each task in the `foreachtask` task.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Aug 2025 05:58:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/access-to-for-each-run-ids-from-jobs-rest-api/m-p/128695#M48319</guid>
      <dc:creator>prabhatika</dc:creator>
      <dc:date>2025-08-18T05:58:42Z</dc:date>
    </item>
  </channel>
</rss>

