Forum Discussion

jasperj101's avatar
jasperj101
Helper I
1 year ago
Solved

Scheduled Refresh Not Pulling New Data

Good Afternoon All,    I have a scheduled refresh of a 2 daily dataflows followed by a scheduled refresh of a semantic model that pulls data from these flows.    I noticed that the data in the da...
Dataflow
  • jasperj101's avatar
    jasperj101
    1 year ago

    Hi All, 

     

    Just to confirm this is now fixed, by changing the timings of the scheduled refresh for both the dataflow and dataset (I shifted them both forward by 30 minutes) this fixed the issue. 

     

    However, I have no idea why this issue occured and the scheduled refreshes were pulling in old data from a fixed point in time without erroring... Any explanatgions would be muich appreciated. 

     

    Thanks, 

    J

Tutu_in_YYC's avatar
Tutu_in_YYC
Super User
1 year ago

Can you let us know the refresh schedule of the dataflow and semantic model? And are you using the option in power bi service or API to refresh them?

jasperj101's avatar
jasperj101
Helper I
1 year ago

Hi, 

 

Dataflows both refresh at 05:30 UTC and take around 5 minutes. 

 

Model then refreshes at 07:00 and 12:00 UTC, takes around 40 minutes. 

 

Scheduled refreshes are configured in the PowerBI sevice. 

  • Tutu_in_YYC's avatar
    Tutu_in_YYC
    Super User
    1 year ago

    I was concerned that there could be overlap between refresh of Dataflow and Semantic model, but you do have enough buffer time between them. Thats good.

    If i understand correctly, scheduled refreshes are all succcessful for both dataflow and semantic model. But when you open the report, the data is 6 days old. 

     

    Can you tell me how did you check if its 6 days old? is it based on a date that you calculated using a function in DAX/Power Query or did you look into the date in the data itself?

     

    One thing you can do to confirm if the tables are really refreshed, is by using SSMS to see when table partition was last processed.

     


    These are possible issues:
    1. Web browser cache

    2. Transformation issues

    3. Dataflow reference in semantic model

    4. Bug in Power BI service