Fabric notebook refresh failures in monitor hub

[Shahhaiderbomb]

I get refresh failures in monitor hub daily about a fabric notebook which I have set to scheduled refresh every day, inside data pipeline. However, when I check my notebook, there are not any refresh failures.

Is anyone else having same issue?

[v-menakakota]

Hi @Shahhaiderbomb ,

Thanks for reaching out to the Microsoft fabric community forum. 

Going forward, it’s possible that the refresh failure you're seeing in the Monitor Hub could be due to a delay or mismatch in reporting between the notebook execution and the monitoring logs. I recommend to review the Data Pipeline activity run that includes the notebook sometimes, the pipeline might fail due to parameter issues or environment constraints, even if the notebook runs fine independently.
If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Best Regards, 
Menaka Kota 
Community Support Team 

[v-menakakota]

Hi  @Shahhaiderbomb ,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster. 

Thank you. 

[v-menakakota]

Hi @Shahhaiderbomb ,

May I ask if you have resolved this issue? If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you. 
 

Thank you,

Community Member.

[v-menakakota]

Hi @Shahhaiderbomb ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you.

Thank you.

[Akash_Varuna · Accepted solution]

Hi @Shahhaiderbomb It might be due to discrepancies between the Monitor Hub logs and the notebook's execution status. Verify execution logs in the notebook and ensure the data pipeline settings are correct. Enable notifications for better tracking, and manually trigger the pipeline to cross-check. This could be caused by a reporting delay or sync issue in the monitoring system.