Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
We have set up an ELT process following the Medallion architecture with Bronze, Silver, Gold, and Config warehouses. We configured a pipeline scheduler to push data from the Bronze to the Gold warehouse every 30 minutes. However, the warehouse GUI does not display the updated refresh time for the Gold and Config warehouse. Additionally, the refresh time is not visible at all for the Silver and Bronze warehouses, even when performing a manual refresh
1. When will the warehouse be automatically refreshed?
2. The semantic model also referehs if the warehouse refresh occurred automatically.?
Solved! Go to Solution.
Hi @Kanna123 ,
I'm assuming you are referring to the default semantic models associated to the warehouses not posting an updated refresh date.
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:
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.
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.
Thanks for your message!! Sorry for the late reply !
We have already used some tables from Silver_Warehouse for Power BI dashboard development, but the Silver_Warehouse still has not updated any timestamps. I also tried adding a new table to the Bronze_Warehouse and refreshed the Warehouse, but no updates were made.
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:
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 ,
I'm assuming you are referring to the default semantic models associated to the warehouses not posting an updated refresh date.
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 @DataBard
Thank you for the clarification regarding the semantic model refresh. However, my question is about the refresh time for the warehouse, which is not updated, even though I am running the pipeline scheduler every 30 minutes. As shown in the screenshot, the Bronze and Silver Warehouses do not display any refresh time.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
2 | |
1 | |
1 | |
1 | |
1 |
User | Count |
---|---|
5 | |
3 | |
3 | |
3 | |
2 |