Forum Discussion
Error message from the 'Get Item Job Instance' endpoint missing details
Hello Konstantin_K,
Based on your screenshots, it does appear that the behavior has changed.
Previously, the Get Item Job Instance endpoint returned the underlying pipeline/notebook error details, whereas it now only returns the generic message: Pipeline run Failed.If this change started around the same time for all pipelines and there were no changes to your implementation, it could be due to a backend service update or API regression rather than an issue with your code.
As a workaround, you could:Check the Pipeline run details in the Fabric portal for the full activity-level error.
Review the Notebook run logs (if the failure originates from a notebook), as they typically contain the detailed exception.
If you're relying on the API for automated monitoring, I'd recommend opening a Microsoft support ticket or raising it through the Fabric Ideas/Community, as the loss of detailed error information impacts troubleshooting and automation scenarios.
It would be useful if Microsoft could clarify whether this is an intentional API change or an issue that will be addressed in a future update.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.
Solution SpecialistHello Konstantin_K,
Based on your screenshots, it does appear that the behavior has changed.
Previously, the Get Item Job Instance endpoint returned the underlying pipeline/notebook error details, whereas it now only returns the generic message: Pipeline run Failed.
If this change started around the same time for all pipelines and there were no changes to your implementation, it could be due to a backend service update or API regression rather than an issue with your code.
As a workaround, you could:
Check the Pipeline run details in the Fabric portal for the full activity-level error.
Review the Notebook run logs (if the failure originates from a notebook), as they typically contain the detailed exception.
If you're relying on the API for automated monitoring, I'd recommend opening a Microsoft support ticket or raising it through the Fabric Ideas/Community, as the loss of detailed error information impacts troubleshooting and automation scenarios.
It would be useful if Microsoft could clarify whether this is an intentional API change or an issue that will be addressed in a future update.
Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant
💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.