Power Automate Cloud Flow Exception Handling and data sync

I need these scenarios addressed if any one need to discuss with me if I like there explanation I can go with them for further discussion Requirement on power automate cloud flows
Scenario 1: Cloud Flow Exception Handling and Monitoring Challenges

In our current Power Automate Cloud implementation, several flows occasionally encounter exceptions. When these errors occur, the flows are automatically turned off by the system without any notification or alert being sent to the support team. Although an exception-handling framework has been implemented, it is not functioning as expected. As a result, failures go unnoticed until users report issues, causing delays and operational impact.
We need to design and implement a robust monitoring and exception-handling mechanism that can:
Track all flow failures in real time
Trigger alerts when a flow is turned off due to errors
Automatically attempt recovery or restart where possible
Provide centralized visibility of flow health and run history
Prevent silent failures and ensure uninterrupted business operations
The goal is to eliminate scenarios where flows stop running unexpectedly without any form of proactive communication.

Scenario 2: SharePoint-Flow Data Sync Failure for Null/Empty Person Fields

In another part of the project, we are facing a data synchronization issue between SharePoint and Power Automate flows. When a Person/People Picker field in SharePoint is updated with a new user, the flow triggers correctly and updates the Azure Storage (data source) as expected. However, when the user is removed from the SharePoint item, the Person field becomes NULL or empty. In this case:The flow either does not trigger Or it triggers but fails during execution
The Azure Storage data does not sync the NULL value.But if we replace the person value (not remove it), everything works correctly.This indicates that the flow logic is not handling NULL/empty values for Person fields, causing failures when SharePoint sends an empty object instead of a user object.We need to enhance the flow logic to properly manage empty or null values in SharePoint Person fields to ensure seamless synchronization with Azure Storage.