Dataflows - Refresh details in the Fabric Monitoring hub

Dataflow Gen2 refreshes appear in the Fabric Monitoring hub today, but the hub surfaces run-level status only. Investigating a failure requires leaving the hub and opening the dataflow's refresh history through Recent runs in the workspace. This feature brings the detailed refresh experience into the Monitoring hub, so users can move from a failed run to its root cause without changing context.Selecting a Dataflow Gen2 refresh entry in the Monitoring hub opens the detailed run view, with the same information available in Recent runs today: overall status, refresh type, duration, request and session identifiers, the tables loaded during the refresh, and the activities performed, including writes to output destinations. Users can drill into an individual table or activity to review errors and activity statistics such as rows and bytes written. Run entries also link directly to the dataflow and the workspace that produced them, so investigation and remediation happen in one place.This also completes the path that begins with a refresh failure notification. The link in a failure email lands the user on the run in the Monitoring hub, and from there they can navigate straight to the failure details rather than locating the dataflow manually.Key benefits and scenarios:* Investigate Dataflow Gen2 refresh failures directly in the Monitoring hub, without navigating back to the workspace to open Recent runs* Drill from a run into per-table and per-activity details, including error messages and output destination statistics* Navigate from a run entry to the originating dataflow and workspace* Monitor and troubleshoot Dataflow Gen2 alongside pipelines and other Fabric items in a single, consistent experienceBy bringing refresh details into the Monitoring hub, Dataflow Gen2 monitoring becomes consistent with the rest of Data Factory and gives data teams one place to detect, diagnose, and resolve refresh issues.