Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Failed to complete the command because the underlying location does not exist LakehouseSQL Endpoint

Our data hasn't been udpated in a week and this query that we have been running has been running successfully for a week until today. We got   SELECT * FROM table WHERE 1=1 AND id = <id>  AND date...
  • nilendraFabric's avatar
    1 year ago

    Hello Anonymous 

     

    The SQL Endpoint’s metadata (table/file references) becomes temporarily out of sync with the actual Delta tables in the Lakehouse. This causes queries to reference outdated file paths (e.g., GUID-based Parquet files that no longer exist). The error code `24596` explicitly indicates this mismatch

     

    This issue was discussed many times in the forum. Although it is never mentioned in known issues in Fabric docs

     

    try Manually trigger a metadata refresh on the Lakehouse via Fabric’s UI to force the SQL Endpoint to sync

     

    Right-click Lakehouse → Refresh

     

    Modify your pipeline to include a retry loop with a 30–60-second wait between attempts

    workarounds like forced refreshes and retries often resolve it. For critical systems, consider using Delta Lake directly

     

    if this is helpful please accept the answer