warehouse GUI does not display the updated refresh time

Hi Kanna123 ,

I'm assuming you are referring to the default semantic models associated to the warehouses not posting an updated refresh date.

1. Default semantic models are set to autorefresh by default, so assuming the tables in your semantic model are Direct Lake, the data should always be up to date.
2. Correct, the semantic model refreshes when the warehouse does. I was able to confirm this in my own environment where the semantic model refreshed date matches when I created the warehouse, but the data I can query from the semantic model is current.
   1. You can find information on this in the settings section of the default semantic model, shown here: 

Hope this helps clarify what to expect. If it does, be sure to accept the desired answer so others in the community can learn from it!

Hi Kanna123 ,
Thanks for posting in Microsoft Fabric Community.

The refresh times for the Gold and Config Warehouses show up initially because they reflect the last time an external action, like a query from Power BI or SQL Server Management Studio (SSMS), or a change to the warehouse structure (like adding a column), took place. However, these times don’t update every 30 minutes when the pipeline pushes data because Fabric doesn’t treat internal processes like pipeline data writes as “refresh events.” The timestamps only change when there’s external activity or a structural update.

Since your pipeline scheduler is pushing data internally (from Bronze to Gold), this process doesn’t trigger an update to the "Refreshed" timestamp.

For the Bronze and Silver Warehouses, the refresh times are not displayed at all because these layers are primarily meant for intermediate data processing, not for external reporting or querying.

To Confirm the Gold and Config Warehouses Are Up-to-Date:
To ensure the data is being refreshed correctly, you can:

1. Run a query on the Gold or Config Warehouses using tools like Power BI or SSMS. This should update the refresh time in the Fabric UI.
2. Check the pipeline logs to confirm that data is successfully being pushed into these warehouses.

If the issue persists after performing these steps, let us know, and we can look into this further or escalate it if needed.

I hope this clarifies why the refresh times behave this way. Let us know if you need additional assistance!

If this post helps, please consider accepting as solution to help others find it easily and a kudos would be much appreciated.


Best Regards,
Vinay.

Hi Kanna123 ,

We haven’t heard from you since our last response and just wanted to check whether the solutions provided addressed your needs. If they did, we’d appreciate it if you could mark the response as the solution to help others benefit from it.

If the issue persists or you need further assistance, please don’t hesitate to reach out.

Thank you.