Forum Discussion

smeetsh's avatar
smeetsh
Icon for Continued Contributor rankContinued Contributor
8 hours ago

SQL Endpoint lakehouse: Intermittent error in the Refresh SQL analytics endpoint activity

Hi All,

since Monday we are having intermittent issues with the Refresh SQL analytics endpoint in our pipelines in fabric.  We run multiple pipelines on an F8 sku, which Monday was about 60% used and today about 70% used, so enough capacity.

I do see there is a Fabric service degradation, but the description doesn't match the issue (though I have seen often enough that that doesn't have to mean anything)

The error is: 
"Error calling the endpoint 'https://api.fabric.microsoft.com'. Response status code: 'ClientSideException HttpStatusCode : 408, HttpStatusString: RequestTimeout'. More details: Exception message: 'NA - Unknown [ClientSideException] A task was canceled.'.

Request didn't reach the server from the client. This could happen because of an underlying issue such as network connectivity, a DNS failure, a server certificate validation or a timeout. Url endpoint request timed out. Please make sure the endpoint response is within 1 minute and retry."



I have implemented a retry on a few of our pipelines but of course as luck would have it the last set of runs was fine and fast. We were very happy with the GA release of the Refresh SQL analytics endpoint activity, since we could get rid of the forced waits we had to build into our pipelines, but this is not much of an improvement if this keeps happening.

Does anyone have any idea? Just a glitch, or (as co-pilot said) "known issue with the acknowledgement of the refresh not reaching the activity.

Cheers

Hans

data pipeline
lakehouse

1 Reply

  • v-sathmakuri's avatar
    v-sathmakuri
    Icon for Community Support rankCommunity Support
    1 hour ago

    Hi smeetsh​ ,

    Thank you for reaching out to fabric community.

    • This is most likely a transient Fabric API timeout not an F8 capacity issue.
    • Add a Retry policy with a delay to the Refresh SQL analytics endpoint activity.
    • Ensure the activity runs after all Lakehouse write / ingestion operations are completed to avoid concurrent update / locking issues.
    • Microsoft's current documentation specifically states that the activity can intermittently fail when other processes are actively updating the underlying Lakehouse, because the SQL analytics endpoint needs to acquire internal locks. However, the exact 408 Request Timeout / A task was canceled error in your example is not explicitly documented as the known issue.

    Refresh SQL analytics endpoint activity - Microsoft Fabric | Microsoft Learn

    Thanks!!