When querying notebook runs via https://learn.microsoft.com/en-us/rest/api/fabric/core/job-scheduler/get-item-job-instance?tabs=HTTP... it always returns the failure message "Job instance failed without detail error" for failed notebook runs without further details.
When I triggered a notebook run via https://learn.microsoft.com/en-us/rest/api/fabric/core/job-scheduler/run-on-demand-item-job?tabs=HTT... and checked the status of this notebook run near real-time, I noticed that shortly after the failure the exception was included in the response, but it disappears after 5 to 10 seconds (see below screenshot).
Always returning the exception details for a failed notebook run, would help understanding why the notebook run failed without the need to jump into the notebook run history and check in the item snapshots what happened.
- hvdv99 on: Detach from a session and Attach later
-
makromer
on:
Fabric Data Pipeline should be able to execute dbt...
- khaoula123 on: Copying values from Power BI visuals should respec...
- hvdv99 on: Lakehouse SQL endpoint table data gets truncated w...
- GertjanIdema on: Enable CI/CD for Dataflow Gen2 across all Fabric S...
-
EHA_SD
on:
Customers should ereceive notifications for all th...
-
miguel
on:
Recent Data and Recent Connections
- hvdv99 on: Cell Conditions in Fabric Notebook
-
frithjof_v
on:
Need more details on Average utilization% in Capac...
-
hedeencharles
on:
Access Variable Library in Semantic Models