Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Due to the restrictions with the scheduling options of pipelines, we have ended up with a master pipeline that kicks off individual runs of our other pipelines using an invoke pipeline activity. The runs invoked this way don't appear in the the Monitoring Hub, making it quite difficult to debug individual runs.
Is there a way of querying the pipeline run history data directly so we can pull together our own report were we can see everything we need in one place?
Many thanks
Mark
Solved! Go to Solution.
Hi @MarkBurgess ,
Response from Internal Team -
The issue is fixed, and rolling out to all regions soon. Tentative ETA end of month.
Hope this is helpful. Please let me know incase of further queries.
Hi @MarkBurgess ,
Thanks for using Fabric Community.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.
HI @v-gchenna-msft , that's great news, thank you.
Regarding the question around accessing the history data behind the monitoring hub, is that a 'no'?
Hi @MarkBurgess ,
At present we don't have any such kind of option.
Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hope this helps. Please let me know if you have any further queries.
Hi @MarkBurgess ,
Response from Internal Team -
The issue is fixed, and rolling out to all regions soon. Tentative ETA end of month.
Hope this is helpful. Please let me know incase of further queries.