Automatic Pipeline Execution at incorrect hour

[vdgarcia]

Hi, today all my scheduled pipelines ran at the same time and this was an incorrect time because they have different scheduling times. I don't know if this issue was a result of a massive failure, how do I know if this issue will occur again tomorrow?

Please note that this issue is the first time it has happened.

Thank you.

[vdgarcia]

Hi Again and thank you, 

How can I see the history of Fabric service failures, so I can identify when a failure has occurred in the past?

Thank you.

[Anonymous · Accepted solution]

Hi @vdgarcia 

There was a known outage in the data pipeline yesterday, which has now been resolved.

​The problem you are experiencing may be related to this issue, please confirm that the current refresh is normal.

​If you have any questions, please contact me. Thank you!

Solved: Pipeline suddenly stopped schedule refreshing - Microsoft Fabric Community

Regards,

Nono Chen

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[vdgarcia]

Hi Again and thank you, 

How can I see the history of Fabric service failures, so I can identify when a failure has occurred in the past?

Thank you.

[Anonymous]

Hi @vdgarcia 

To view the history of Fabric service failures, you can use Service Fabric Explorer or Azure Monitor.

Open the Service Fabric Explorer.

Navigate to Events to see a list of recent events, including failures.

You can filter and search for specific types of failures or time periods.

Visualizing your cluster using Azure Service Fabric Explorer - Azure Service Fabric | Microsoft Lear...

Go to the Azure portal and select "Monitor."

Under Logs, you can query the logs of the Service Fabric cluster.

Use queries to filter by failed events and specific time ranges.

Monitor Azure Service Fabric - Azure Service Fabric | Microsoft Learn

Regards,

Nono Chen

[vdgarcia]

Hi @Anonymous thank you for your reply.

I need to know how to obtain the history of the Microsoft Fabric platform status, instead of the current status of the platform which only shows me how it is now, and does not allow me to identify if an event that occurred in the past could be related to a failure of my pipelines.

[DavidCousins]

That is Azure "Service Fabric" not Fabric.