i am getting the below error while making a GET request to job in databrick after successfully running it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2022 12:08 AM
"error_code": "INVALID_PARAMETER_VALUE",
"message": "Retrieving the output of runs with multiple tasks is not supported. Please retrieve the output of each individual task run instead."
}
- Labels:
-
Databricks V2
-
Job
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2022 08:09 AM
Looks like the request was malformed (error code: 400) . You can retrieve the details for a single job running GET API.
Please refer: https://docs.databricks.com/dev-tools/api/latest/jobs.html?&_ga=2.42546021.1557771202.1661376549-162...
Could you please provide the body of the request?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-05-2022 08:39 PM
Hi debayan ,the body of this request has only job id as key and its value .I am unable to find the solution .can u please provide some other solution to it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2022 02:03 AM
I believe this is a bug in API 2.1 of Databricks
I had the same issue but after lot of hit and trails I changed the GET url to https://xxxxxxxx.cloud.databricks.com/api/2.0/jobs/runs/get-output?run_id=1863081801 and surprisingly it worked.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2024 04:12 PM
@CJay thanks for this, your solution to downgrade the API version to 2.0 helped me as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2022 11:27 AM
Could you please update the API endpoint you are using so that we can check and update you with the same? @Himanshu yadav
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2022 12:13 AM
@Atanu Sarkar I belive he is using https://<databricks-instance>/api/2.1/jobs/get-output?run_id=xxxx
Even we are also facing the same problem while retrieving run status.
Can you please check and let us know?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-18-2022 06:51 AM
try 2.0 instead of 2.1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2022 10:06 AM
Same issue...switching to 2.0 resolved it. Thanks @Chandrajeet Singh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2022 08:44 PM
Use https://<databricks-instance>/api/2.1/jobs/runs/get?run_id=xxxx.
"get-output" gives the details of single run id which is associated with the task but not the Job.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2024 12:43 PM
Thanks! That worked in my case
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2025 11:38 PM - edited 02-13-2025 11:39 PM
I am getting the same issue for the get-output endpoint for both 2.2 and 2.1 versions of the API
https://${databricks-instance}/api/2.2/jobs/runs/get-output?run_id=${run_id}
But interestingly the 2.0 version works like magic
https://${databricks-instance}/api/2.2/jobs/runs/get-output?run_id=${run_id}
Databricks team - Can you look into this and fix this at the earliest?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
In order to get the output using the 2.2 API version you should use the task run id instead of the job run id.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Hi @Debayan
I'd suggest to also mention this explicitly in the documentation of the workspace client for get_run_output
One has to pay extra attention to the example
run_id=run.tasks[0].run_id
otherwise it can be easily missed. 🙂

