A scheduled Dataflows Gen2 in Microsoft Fabric loads several Lakehouse tables and its overnight refresh failed. The engineer opens the run history and sees the refresh listed with a failed status, but needs to know which specific query inside the dataflow failed and the error text that query returned before correcting the offending step. Which detail in the Dataflows Gen2 refresh history most directly identifies the failing query and its error?
- AThe per-query refresh details, which list each query in the dataflow with its own status and the error message returned for the query that failed. Correct
- BThe capacity utilisation chart for the workspace, which shows whether the dataflow consumed enough compute units during the failed refresh.
- CThe Lakehouse table lineage view, which shows which destination tables the dataflow writes to and how they connect downstream.
- DThe workspace Git commit history, which records when the dataflow definition was last changed and by whom before the refresh failed.
Why A is correct: Dataflows Gen2 refresh history records the outcome of each query separately, so the per-query details point straight to the failing query and its error message.
Why B is wrong: Capacity utilisation can hint at throttling but does not name which query failed or return the query-specific error text the engineer needs to fix the step.
Why C is wrong: Lineage shows data flow relationships between items but carries no refresh status or error message, so it cannot reveal which query failed.
Why D is wrong: Commit history tracks definition changes for version control and contains no runtime refresh outcome, so it cannot identify the failing query or its error.