Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
Anonymous
Not applicable

Scheduled Refresh chronology bug

I am using an incremental model which is scheduled to run every morning at 7:30 AM. The refresh should take about 1h 45mins, however with this refresh a weird thing happened: after about 5 hours on the status column the Timeout status came out but without the End Time. The next day, more than 24H later, the End Time is visible and the status being updated to Complete, as you can see in the next image. 

adri_cano_0-1617119617664.png

The same thing was repeated a couple of days later. From the Capacity Metric dashboard I can see that it also clogs the memory consumption for the whole time causing problems with other datasets in our Premium capacity. 

This seems like a bug to me. Does anyone know anything more about this? 

 

1 REPLY 1
selimovd
Super User
Super User

Hello @Anonymous ,

 

did you check your data source?

Is it possible that it really took so long? I experienced something like that in the past.

 

If you need any help please let me know.
If I answered your question I would be happy if you could mark my post as a solution ✔️ and give it a thumbs up 👍
 
Best regards
Denis
 

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.