Fabric Shortcuts have a delay reflecting changes to data in tables living in the warehouse

[jacarmonaro]

Hi, I have a lakehouse and a warehouse in Fabric in the same workspace. I also have a shortcut in my lakehouse pointing to XYZ's table in the warehouse. I run inserts and updates on the XYZ table in the warehouse. When I invoke the shortcut in the lakehouse, the output does not reflect the latest modifications to the data. If I wait 5 to 10 minutes and then invoke the shortcut again, the output now reflects those changes to the data.

Is this a behavior people are experiencing? Is there an expected delay for a shortcut to reflect the latest changes in the data coming out from a warehouse in Fabric? Is there any suggestion to bypass this issue?

[v-prasare]

We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?

If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.

Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.

Thank you for your understanding and participation.

[v-prasare]

Hi @jacarmonaro,

Thanks for actively participating in MS Fabric community.

The latency delays you're experiencing when using a shortcut from a Lakehouse to a Warehouse in Fabric is an expected behaviour. as @suparnababu8 mentioned the delay is due to Fabric scheduled refresh intervals or metadata sync. Microsoft Fabric prioritizes performance and cost optimization over instant refresh.

Why is there a latency delay in shortcuts?

Why doesn’t the Lakehouse reflect immediate changes:  Shortcuts in Fabric rely on the OneLake caching layer to improve query performance. This layer creates a temporary snapshot of the data from the Warehouse. The snapshot is refreshed on a schedule, usually few minutes.

Here are a few ways you can address this issue:

• Instead of relying on a shortcut, you can create a Direct Query connection from the Lakehouse to the Warehouse
• You can create a Fabric Notebook to automate the cache refresh using the REFRESH command: REFRESH  <shortcut_name>;

Thanks,

Prashanth Are

MS Fabric community support.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos"

[JonMoz]

Hi @v-prasare , is there any documentation around using that REFRESH command? I haven't been able to get it to work.

I've also tried the Reset Shortcut Cache API call but I just get a 500 internal error.

Thanks

Jon

[danieletiles]

Hi @v-prasare ,

what you're writing is very interesting, can you please provide a link to a Microsoft Learn resource that describe this behaviour of Fabric Shortcuts?

Thanks!!

Daniele

[v-prasare]

Hi @danieletiles, Thanks for actively participating in MS Fabric community support.

Please refer to below for Fabric shortcut limitations and considerations:
microsoft fabric shortcyts latency microsoft learn sources

similar threads and articles where shorcut latency described:
Solved: fabric shortcuts - Microsoft Fabric Community
Internals of ‘Shortcuts’ feature in Microsoft Fabric

Thanks,

Prashanth Are

MS Fabric community support.

[jacarmonaro]

Now, I see my shortcuts stop updating the info. They are displaying a version of data as of 01-08. Deleting and re-creating the shortcut has not fixed this new issue. Has anyone experienced this situation? Is there a workaround, or something I can do to force the shortcut refresh?

[v-prasare · Accepted solution]

Hi @jacarmonaro,

In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks,

Prashanth Are

MS Fabric community support.

Did I answer your question? Mark my post as a solution, this will help others!

If my response(s) assisted you in any way, don't forget to drop me a "Kudos"

[suparnababu8]

Hi @jacarmonaro 

Yes, the behavior you're experiencing with the delay in reflecting the latest data changes through a shortcut in Microsoft Fabric is known and has been experienced by me also. This delay is typically due to the time it takes for the metadata synchronization between the warehouse and the lakehouse.  Let's wait until fix it from Microsoft. Thanks