Forum Discussion
PowerBI Dataflows Scheduled Refresh Failures 0xE4210002
Hi,
I have a range of scheduled dataflow refreshes on 2 different F64 premium workspaces, these usually work however, once or twice per week one or many of the dataflows will fail the scheduled refresh which occurs at 05:30 UTC. This seems to happen at random intervals and to different dataflows each time, although sometimes multiple dataflows will fail simultaneously.
They always have the following error message and exit code: "Error: PipelineException: Container unexpectedly exited. Exit code: 0xE4210002." Any information on why this occurs would be greatly appreciated ๐
2 Replies
- AnonymousNot applicable
Hi, jasperj101
You might be able to go to your workspace settings > Premium > license mode, change from an existing Premium capacity to Pro, then repeat and switch back to the Premium capacity, select the same capacity and apply. You can refer to the following link:
Solved: Dataflow Refresh Failure: Container unexpectedly e... - Microsoft Fabric Community
Sometimes, running out of resources can cause the container to exit unexpectedly. Or disable scheduled refresh and republish the semantic model.
Troubleshoot refresh scenarios - Power BI | Microsoft Learn
You can also take a look at the refresh limits and known issues for dataflowsDataflow Gen2 refresh - Microsoft Fabric | Microsoft Learn
Fabric known issues - Microsoft Fabric | Microsoft Learn
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- Poojara_D12
Super User
Hi jasperj101
As per my understanding:Check Premium Capacity Resource Utilization:
- Review the capacity utilization metrics in the Power BI Admin portal to ensure that the Premium capacity isnโt under heavy load during the scheduled refresh. If it's overutilized, consider increasing the capacity or reducing the number of concurrent refreshes.
Increase Dataflow Timeout:
- If the dataflows are large or complex, consider increasing the timeout setting for dataflow refreshes. You can do this by optimizing your queries or breaking the dataflow into smaller parts.
Check for Transient Power BI Service Issues:
- Check the Power BI Service status to see if there are any known outages or maintenance periods happening during the refresh times. Sometimes, issues are related to service disruptions.
Stagger Refresh Schedules:
- If multiple dataflows are running at the same time, consider staggering the scheduled refresh times to reduce the load on the capacity.
Monitor Gateway and Data Source Connectivity:
- Ensure the On-Premises Data Gateway (if used) is running properly and has no connectivity issues with the data sources. Intermittent network issues or database timeouts can cause dataflow refresh failures.
Retry Failed Refreshes:
- If a dataflow fails due to a transient issue, you can manually retry the failed refresh or set up a retry mechanism to handle such errors more gracefully.
Also,
The error typically results from resource limitations, transient service issues, or connectivity problems. To resolve it, check the capacity usage, consider staggering dataflow schedules, optimize the dataflows, and monitor the Power BI service status for potential disruptions. If the issue persists, you may need to reach out to Microsoft Support for further investigation, especially if it's related to a service issue or underlying infrastructure problem.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" ๐
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS