Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Hi Everybody,
this is my first post, so I hope I found the right place to write my issue.
I'm currently managing a solution in Fabric that it's next to be released in production, but in the last 10 days I started having issues in my test workspace. Nothing is changed, we created a test workspace to let final users to test my work before going in production.
My overall architecture is as follows (basically a medallion architecture):
- bronze layer: views on DWH reading data ingested in a LH with an Oracle Gateway
- silver layer: in DWH, it contains the ETL logic, including facts and dimensions
- gold layer: in DWH
The final semantic model is fully based on gold layer tables, in Direct Lake mode.
The ETL logic in gold layer have basically 3 scenarios:
In gold layer, when no aggregation and no calculated columns is needed, I use the following approach:
drop table if exists gold.TABLE_X
create table gold.TABLE_X as clone of silver.TABLE_X
Everything worked smoothly since last week, when I started having problems in refreshing semantic model: usually it took 10 to 15 seconds to refresh, now refreshing runs for nearly 10 minutes and then it fails with the following error:
Data source error: COM error: Azure.Storage.Files.DataLake, The specified path does not exist.
RequestId:a360f7c1-f01f-0041-098d-cc4ed4000000
Time:2025-05-24T09:22:23.3943008Z
Status: 404 (Not Found)
ErrorCode: PathNotFound
Content:
{"error":{"code":"PathNotFound","message":"The specified path does not exist.\nRequestId:a360f7c1-f01f-0041-098d-cc4ed4000000\nTime:2025-05-24T09:22:23.3943008Z"}}
Headers:
Access-Control-Allow-Headers: REDACTED
Access-Control-Allow-Methods: REDACTED
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: REDACTED
x-ms-error-code: PathNotFound
x-ms-request-id: a360f7c1-f01f-0041-098d-cc4ed4000000
x-ms-version: 2024-08-04
x-ms-client-request-id: 9767caa5-2d39-4a18-8da9-25cc335c81b4
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-root-activity-id: REDACTED
InternalRouteType: REDACTED
Date: Sat, 24 May 2025 09:22:22 GMT
Server: Windows-Azure-HDFS/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Content-Length: 163
Content-Type: application/json; charset=utf-8
. Table: TABLE_X.
If then I re-run the refresh, then it fails (after again 10 minutes) with the same issue, but pointing to another table, let's say TABLE_Y
This seems to happen just with the CLONE OF statetement
The only way I found to fix the issue it to rerun the part of pipeline that runs gold layer and then the refresh goes fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.