Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
Hello,
We have a suite of executive reports that are delivered on a weekly basis via a Power Automate flow that runs the report builder reports, archives the Excel files in a Sharepoint folder, and sends an email with a link to the most recent files to the report users. If the flow detects that any or all of the files have not been properly archived (generally due to a report failure) we are notified via a Teams message and the email isn't sent until the flow runs properly.
However, each of the main reports in the suite executes multiple sub-reports which will on rare occasions fail to render. Because the main report processes successfully and the file is archived as expected, the only way for us to have visibility to these sub-report failures is to manually review each tab of each Excel file to ensure all of them rendered correctly.
Is there a way for us to have some kind of notification or other visibility to these sub-report failures? Ideally I believe that we would like something that could be built into the flow so that we copuld attempt to re-run the impacted reports, but any kind of notification would be helpful.
Solved! Go to Solution.
Hi @aaroncampeau,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Here are the suggestions:
Error Flag in Main Report: Modify the main SSRS report to include an error flag or status from each sub-report, so Power Automate can detect issues by checking this flag after report generation.
Excel Tab Check in Power Automate : Add a step in the flow to list and validate the worksheet names in the generated Excel file; if any expected tab is missing, trigger a notification or retry.
Script-Based Excel Validation : Use a PowerShell script or Azure Function to inspect Excel files for missing tabs or rendering errors, then pass the result to Power Automate for further action.
Database Logging from Sub-reports : Have sub-reports write their execution status to a central SQL table, which the flow can query to check for failures before sending final output.
Status Tab in Reports : Include a dedicated tab in each report summarizing sub-report success or failure, which Power Automate can scan for a quick health check.
If you find this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to support others in the community.
Thank you & regards,
Prasanna Kumar
Hi @aaroncampeau,
Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.
If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful — this will benefit others in the community as well.
Best regards,
Prasanna Kumar
Hi @aaroncampeau,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Here are the suggestions:
Error Flag in Main Report: Modify the main SSRS report to include an error flag or status from each sub-report, so Power Automate can detect issues by checking this flag after report generation.
Excel Tab Check in Power Automate : Add a step in the flow to list and validate the worksheet names in the generated Excel file; if any expected tab is missing, trigger a notification or retry.
Script-Based Excel Validation : Use a PowerShell script or Azure Function to inspect Excel files for missing tabs or rendering errors, then pass the result to Power Automate for further action.
Database Logging from Sub-reports : Have sub-reports write their execution status to a central SQL table, which the flow can query to check for failures before sending final output.
Status Tab in Reports : Include a dedicated tab in each report summarizing sub-report success or failure, which Power Automate can scan for a quick health check.
If you find this response helpful, please consider marking it as the accepted solution and giving it a thumbs-up to support others in the community.
Thank you & regards,
Prasanna Kumar
Thank you so much! This looks like it will give us what we need.
User | Count |
---|---|
12 | |
3 | |
2 | |
2 | |
2 |