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!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Hello, I have a problem in the scheduled update of transactions in a transaction table of my Power BI dataset. Users report to me that some transactions are missing from their Power BI reports despite the scheduled refresh tasks in Power BI being completed successfully and the SQL Database at the source of the report displaying all the transactions.
The scheduled task takes about 45 to 50 minutes to execute and everything goes perfectly. When I open the report in Power BI Desktop and open and refresh the Power Query with pressing the Transform Data button, sometimes the data is displayed in the grid. I refresh this table grid and push back into my Power BI service and the missing transactions appear.
Initially I thought it could be due to a Timeout between the SQL server and Power BI so I put 1h30 delay. But nothing helps.
Is this the limitation of the Pro license? Or even a performance limit for the transaction table that is not incrementally refreshed?
This question has never been answered. I still have the same problems and it's mainly for my transaction table.
The way I found to solve this automated refresh problem is really annoying.
1 - Each time I have to download the dataset locally.
2 - I make sure to clear the cache (I'm not sure it makes a difference but I'm not taking a chance)
3- I update locally and then I publish in the workspace.
When I have completed these 3 steps, I am able to see the transactions.
Could the commandtimeout at 1 hour 30 minutes be the problem or the pro license I have? Does the cache have a physical limit on the service?
Hi @Anonymous
From the sounds of things it sounds like a timing issue where the dataset is being refreshed (which takes 50mins) but during those 50mins there could be more transactions which are not included in the current load?
What happens if you refresh the dataset over night are all the transactions there? If so then it would indicate more of a timing issue.
I personally have never seen any data lost when refreshing to the Power BI Service (But I have seen filters and timing challenges)
Yeah, that's what I find a bit scary. I scheduled updates every 2 hours because this is one of the client's requirements. As I said, I can see the latest transactions in the SQL source but not in Power BI. The scheduled task to Power BI completed successfully but without the latest transactions. At first I had timeout errors, so I changed the CommandTimeout functionality to allow 1hours 30 minutes timeouts. But that hasn't changed.